Gentoo Archives: gentoo-alt

From: Alan Hourihane <alanh@×××××××××××××××××.uk>
To: gentoo-alt@l.g.o
Subject: Re: [gentoo-alt] Having a persistent bash environment variable
Date: Mon, 04 Feb 2008 19:33:32
Message-Id: 1202153606.11765.13.camel@localhost
In Reply to: Re: [gentoo-alt] Having a persistent bash environment variable by Fabian Groffen
1 On Sat, 2008-02-02 at 00:04 +0100, Fabian Groffen wrote:
2 > On 01-02-2008 21:04:02 +0000, Alan Hourihane wrote:
3 > > > > > While I think this is mainly a Portage related question, still can you
4 > > > > > explain why you want/need to do this? Or what you want to achieve?
5 > > > >
6 > > > > Because the libc I'm using read's an environment variable to determine
7 > > > > functionality, and the emerge process is removing it and changing the
8 > > > > way libc reacts.
9 > > >
10 > > > Feels like we need to know which environment variable this is and add it
11 > > > to Portage's lists.
12 > >
13 > > It's called UNIXMODE. But where do I add it in Portage's list ??
14 >
15 > Can you explain how exactly you set UNIXMODE? For understanding, what
16 > OS/libc is this, and what is the Portage version you use?
17
18 Actually, it's an Atari Falcon (m68k) running FreeMiNT.
19
20 > Do I understand correctly if I say that you set UNIXMODE in your
21 > environment, call portage and that you find that the
22 > compilation/installation doesn't seem to have UNIXMODE set?
23
24 Yes. I've fixed this currently with adding
25
26 export UNIXMODE=....
27
28 at the top of ebuild.sh
29
30 > Wild idea, have you tried setting UNIXMODE in etc/make.conf?
31
32 That's one of the first things I tried, no luck.
33
34 I've got through all of the bootstrap process, and now starting emerging
35 the basics, but I've bumped into some more bash crashes, as I'm getting
36 these errors....
37
38 >>> Compiling source
39 in /root/gentoo/var/tmp/portage/sys-apps/sed-4.1.5/work/sed-4.1.5 ...
40 * The ebuild phase 'compile' has exited unexpectedly. This type of
41 * behavior is known to be triggered by things such as failed variable
42 * assignments (bug #190128) or bad substitution errors (bug #200313).
43
44 * Messages for package sys-apps/sed-4.1.5:
45
46 * The ebuild phase 'compile' has exited unexpectedly. This type of
47 * behavior is known to be triggered by things such as failed variable
48 * assignments (bug #190128) or bad substitution errors (bug #200313).
49
50 which seems to be crashing when setting host_cpu. I'll try and figure
51 that out.
52
53 How do I go about sending patches in to get into the tree so I don't
54 lose the current patches when I do an emerge --sync ??
55
56 Alan.
57
58 --
59 gentoo-alt@l.g.o mailing list

Replies

Subject Author
Re: [gentoo-alt] Having a persistent bash environment variable Fabian Groffen <grobian@g.o>