| 1 |
On Mon, 2008-02-04 at 20:42 +0100, Fabian Groffen wrote: |
| 2 |
> On 04-02-2008 19:33:26 +0000, Alan Hourihane wrote: |
| 3 |
> > > Can you explain how exactly you set UNIXMODE? For understanding, what |
| 4 |
> > > OS/libc is this, and what is the Portage version you use? |
| 5 |
> > |
| 6 |
> > Actually, it's an Atari Falcon (m68k) running FreeMiNT. |
| 7 |
> |
| 8 |
> :) This makes me smile. :) |
| 9 |
|
| 10 |
Me too. |
| 11 |
|
| 12 |
> > > Do I understand correctly if I say that you set UNIXMODE in your |
| 13 |
> > > environment, call portage and that you find that the |
| 14 |
> > > compilation/installation doesn't seem to have UNIXMODE set? |
| 15 |
> > |
| 16 |
> > Yes. I've fixed this currently with adding |
| 17 |
> > |
| 18 |
> > export UNIXMODE=.... |
| 19 |
> > |
| 20 |
> > at the top of ebuild.sh |
| 21 |
> |
| 22 |
> Ok, that's a crude hack, I'll ask around to see how we can do this |
| 23 |
> properly. |
| 24 |
|
| 25 |
Right, please do, I'd love to hear the correct solution. |
| 26 |
|
| 27 |
> > > Wild idea, have you tried setting UNIXMODE in etc/make.conf? |
| 28 |
> > |
| 29 |
> > That's one of the first things I tried, no luck. |
| 30 |
> > |
| 31 |
> > I've got through all of the bootstrap process, and now starting emerging |
| 32 |
> > the basics, but I've bumped into some more bash crashes, as I'm getting |
| 33 |
> > these errors.... |
| 34 |
> > |
| 35 |
> > >>> Compiling source |
| 36 |
> > in /root/gentoo/var/tmp/portage/sys-apps/sed-4.1.5/work/sed-4.1.5 ... |
| 37 |
> > * The ebuild phase 'compile' has exited unexpectedly. This type of |
| 38 |
> > * behavior is known to be triggered by things such as failed variable |
| 39 |
> > * assignments (bug #190128) or bad substitution errors (bug #200313). |
| 40 |
> > |
| 41 |
> > * Messages for package sys-apps/sed-4.1.5: |
| 42 |
> > |
| 43 |
> > * The ebuild phase 'compile' has exited unexpectedly. This type of |
| 44 |
> > * behavior is known to be triggered by things such as failed variable |
| 45 |
> > * assignments (bug #190128) or bad substitution errors (bug #200313). |
| 46 |
> > |
| 47 |
> > which seems to be crashing when setting host_cpu. I'll try and figure |
| 48 |
> > that out. |
| 49 |
> |
| 50 |
> Hmmm, I can't help you with this for the moment, what Portage version |
| 51 |
> and what bash version are you using? |
| 52 |
|
| 53 |
I'm using portage-prefix 9233 currently with bash 3.2(0) and tried |
| 54 |
3.2(33), although I believe anything higher than (20) triggers the usual |
| 55 |
problems. |
| 56 |
|
| 57 |
> > How do I go about sending patches in to get into the tree so I don't |
| 58 |
> > lose the current patches when I do an emerge --sync ?? |
| 59 |
> |
| 60 |
> The tree is an svn tree, so no changes in the tree will be lost. Your |
| 61 |
> change in ebuild.sh will get lost as soon as you update portage. |
| 62 |
|
| 63 |
O.k. I can deal with the ebuild.sh modification for now until we get a |
| 64 |
more definitive answer. |
| 65 |
|
| 66 |
What about changes to the bootstrap-prefix.sh ? |
| 67 |
|
| 68 |
Alan. |
| 69 |
|
| 70 |
-- |
| 71 |
gentoo-alt@l.g.o mailing list |
Archives