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