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