Mailing List Archive

On 06-04-2006 16:58:41 -0700, m h wrote:
> Hey Folks-
>
> I haven't spammed anyone for a week (or tried doing PREFIXy stuff
> during that time). I'm going to be trying it on Ubuntu for the next
> week or so. I noticed there was some chatter about broken ROOT and
> whatnot on the IRC channel. Should I start with 2.1.14? (Or is it
> severely broken?)

For Kito :)

> Also, any update from the bootstrap script side? ;)

I made some changes to beautify it, but I haven't tested it yet on
linux. It should detect Linux itself now, but I think there are some
bugs in it still. So, bleeding edge, but you seem to like that, so go
go go :)


--
Fabian Groffen
Gentoo for Mac OS X Project
--
gentoo-osx@gentoo.org mailing list

On 07-04-2006 08:30:39 +0200, Grobian wrote:
> On 06-04-2006 16:58:41 -0700, m h wrote:
> > Also, any update from the bootstrap script side? ;)
>
> I made some changes to beautify it, but I haven't tested it yet on
> linux. It should detect Linux itself now, but I think there are some
> bugs in it still. So, bleeding edge, but you seem to like that, so go
> go go :)

Sorry, I forgot. That's the problem with wikis IMHO, I made some
extensions to "the" wiki page. I hope they are still there, but they
describe some ideas of changing the bootstrap process somehow, such that
the newly created prefix isn't spoiled with bootstrap junk. Also, on
linux, binutils should be added to the current bootstrap, but I'd like
to figure out if the provided linker can't be used for that to speed up
bootstrapping.


--
Fabian Groffen
Gentoo for Mac OS X Project
--
gentoo-osx@gentoo.org mailing list

I'm proceeding with 2.1.14...

New issue I've run into so far:

Complaint that "emake" wasn't found, which is found in
usr/portage/bin. I added ${PREFIX}/usr/portage/bin to DEFAULT_PATH in
make.globals and continued. Not sure if this is a regression (could
be user error).

-matt

--
gentoo-osx@gentoo.org mailing list

On 07-04-2006 18:54:44 -0700, m h wrote:
> Complaint that "emake" wasn't found, which is found in
> usr/portage/bin. I added ${PREFIX}/usr/portage/bin to DEFAULT_PATH in
> make.globals and continued. Not sure if this is a regression (could
> be user error).

I've had this too. Setting DEFAULT_PATH means you override it, not
append to it. Copy the path from make.globals and add the paths to that
line to get what you expect.


--
Refugee
--
gentoo-osx@gentoo.org mailing list

On 4/8/06, grobian@gentoo.org <grobian@gentoo.org> wrote:
> On 07-04-2006 18:54:44 -0700, m h wrote:
> > Complaint that "emake" wasn't found, which is found in
> > usr/portage/bin. I added ${PREFIX}/usr/portage/bin to DEFAULT_PATH in
> > make.globals and continued. Not sure if this is a regression (could
> > be user error).
>
> I've had this too. Setting DEFAULT_PATH means you override it, not
> append to it. Copy the path from make.globals and add the paths to that
> line to get what you expect.
>

Just clarifying here. You mean hardcode the path to emake int the
ebuild which calls it?

-matt

--
gentoo-osx@gentoo.org mailing list

On 10-04-2006 20:25:24 +0000, m h wrote:
> On 4/8/06, grobian@gentoo.org <grobian@gentoo.org> wrote:
> > On 07-04-2006 18:54:44 -0700, m h wrote:
> > > Complaint that "emake" wasn't found, which is found in
> > > usr/portage/bin. I added ${PREFIX}/usr/portage/bin to DEFAULT_PATH in
> > > make.globals and continued. Not sure if this is a regression (could
> > > be user error).
> >
> > I've had this too. Setting DEFAULT_PATH means you override it, not
> > append to it. Copy the path from make.globals and add the paths to that
> > line to get what you expect.
> >
>
> Just clarifying here. You mean hardcode the path to emake int the
> ebuild which calls it?

No, if you set DEFAULT_PATH in your make.conf, make sure you start by
modifying what is in make.globals. The one in make.globals is like the
default setting, and if you set it, you lose the defaults. (like then
you do "export PATH=$HOME/bin" in bash for instance).


--
Fabian Groffen
--
gentoo-osx@gentoo.org mailing list

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

--
gentoo-osx@gentoo.org mailing list