On Mon, 2008-02-04 at 20:42 +0100, Fabian Groffen wrote: > On 04-02-2008 19:33:26 +0000, Alan Hourihane wrote: > > > Can you explain how exactly you set UNIXMODE? For understanding, what > > > OS/libc is this, and what is the Portage version you use? > > > > Actually, it's an Atari Falcon (m68k) running FreeMiNT. > > :) This makes me smile. :)
Me too. > > > Do I understand correctly if I say that you set UNIXMODE in your > > > environment, call portage and that you find that the > > > compilation/installation doesn't seem to have UNIXMODE set? > > > > Yes. I've fixed this currently with adding > > > > export UNIXMODE=.... > > > > at the top of ebuild.sh > > Ok, that's a crude hack, I'll ask around to see how we can do this > properly. Right, please do, I'd love to hear the correct solution. > > > Wild idea, have you tried setting UNIXMODE in etc/make.conf? > > > > That's one of the first things I tried, no luck. > > > > I've got through all of the bootstrap process, and now starting emerging > > the basics, but I've bumped into some more bash crashes, as I'm getting > > these errors.... > > > > >>> Compiling source > > in /root/gentoo/var/tmp/portage/sys-apps/sed-4.1.5/work/sed-4.1.5 ... > > * The ebuild phase 'compile' has exited unexpectedly. This type of > > * behavior is known to be triggered by things such as failed variable > > * assignments (bug #190128) or bad substitution errors (bug #200313). > > > > * Messages for package sys-apps/sed-4.1.5: > > > > * The ebuild phase 'compile' has exited unexpectedly. This type of > > * behavior is known to be triggered by things such as failed variable > > * assignments (bug #190128) or bad substitution errors (bug #200313). > > > > which seems to be crashing when setting host_cpu. I'll try and figure > > that out. > > Hmmm, I can't help you with this for the moment, what Portage version > and what bash version are you using? I'm using portage-prefix 9233 currently with bash 3.2(0) and tried 3.2(33), although I believe anything higher than (20) triggers the usual problems. > > How do I go about sending patches in to get into the tree so I don't > > lose the current patches when I do an emerge --sync ?? > > The tree is an svn tree, so no changes in the tree will be lost. Your > change in ebuild.sh will get lost as soon as you update portage. O.k. I can deal with the ebuild.sh modification for now until we get a more definitive answer. What about changes to the bootstrap-prefix.sh ? Alan. -- [email protected] mailing list
