1 |
On 19-05-2008 10:57:58 +0200, Bacchella Fabrice wrote: |
2 |
> |
3 |
> Le 19 mai 08 à 08:33, Markus Duft a écrit : |
4 |
> |
5 |
>>> |
6 |
>>> in function bootstrap_tree, when directories are created |
7 |
>>> for x in etc usr/{,s}bin var/tmp var/lib/portage var/log/ |
8 |
>>> portage var/db; |
9 |
>>> do |
10 |
>>> [[ -d ${ROOT}/${x} ]] || mkdir -p "${ROOT}/${x}" |
11 |
>>> done |
12 |
>>> I think {,s}bin. It breaks the installation of bash, and so $EPREFIX/ |
13 |
>>> bin/sh is missing, and that breaks the gcc installation. |
14 |
>> |
15 |
>> This worked many times on different platforms for me. I can't see how |
16 |
>> this should break bootstrap? Why do you think, the {,s}bin is |
17 |
>> the problem? I have bin/sh in the right places in my prefixes... |
18 |
> |
19 |
> It breaks silently for Solaris x86_64 during the installation of |
20 |
> bash-3.2_p17-r1. And latter, the installation of gcc stopped, because |
21 |
> config.sub is launched by $EPREFIX/bin/sh. |
22 |
|
23 |
Maybe that ebuild is wrong anyway, because it should reference |
24 |
$EPREFIX/bin/bash instead... |
25 |
|
26 |
>>> And in the bash ebuild, I think that you could had |
27 |
>>> CFLAGS_FOR_BUILD="$CFLAGS". I don't know why, but that's the CFLAGS |
28 |
>>> using by bash for building. |
29 |
>> |
30 |
>> CFLAGS are passed correctly to bash build. Of that I am sure (haven't |
31 |
>> tried right now though), since on interix I must pass custom |
32 |
>> flags (which works, otherwise I couldn't build...). Could it be that |
33 |
>> CFLAGS_FOR_BUILD is set to CFLAGS somewhere by configure or so, |
34 |
>> if it's not set? This at least sounds plausible to me :) |
35 |
> |
36 |
> It's needed for a 64 bits build. Without it, some part of it are using |
37 |
> 32bits. |
38 |
|
39 |
Hmmmm... interesting |
40 |
|
41 |
|
42 |
-- |
43 |
Fabian Groffen |
44 |
Gentoo on a different level |
45 |
-- |
46 |
gentoo-alt@l.g.o mailing list |