| 1 |
On 4/10/06, Grobian <grobian@g.o> wrote: |
| 2 |
> On 10-04-2006 20:25:24 +0000, m h wrote: |
| 3 |
> > On 4/8/06, grobian@g.o <grobian@g.o> wrote: |
| 4 |
> > > On 07-04-2006 18:54:44 -0700, m h wrote: |
| 5 |
> > > > Complaint that "emake" wasn't found, which is found in |
| 6 |
> > > > usr/portage/bin. I added ${PREFIX}/usr/portage/bin to DEFAULT_PATH in |
| 7 |
> > > > make.globals and continued. Not sure if this is a regression (could |
| 8 |
> > > > be user error). |
| 9 |
> > > |
| 10 |
> > > I've had this too. Setting DEFAULT_PATH means you override it, not |
| 11 |
> > > append to it. Copy the path from make.globals and add the paths to that |
| 12 |
> > > line to get what you expect. |
| 13 |
> > > |
| 14 |
> > |
| 15 |
> > Just clarifying here. You mean hardcode the path to emake int the |
| 16 |
> > ebuild which calls it? |
| 17 |
> |
| 18 |
> No, if you set DEFAULT_PATH in your make.conf, make sure you start by |
| 19 |
> modifying what is in make.globals. The one in make.globals is like the |
| 20 |
> default setting, and if you set it, you lose the defaults. (like then |
| 21 |
> you do "export PATH=$HOME/bin" in bash for instance). |
| 22 |
> |
| 23 |
> |
| 24 |
I've only been editing the make.globals one.... are you suggesting I |
| 25 |
edit it in make.conf now? |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-osx@g.o mailing list |
Archives