Re: [gentoo-user-fr] [AMD64] sandbox

[Didier Link]

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1



Le Fri, 18 Jan 2008 13:19:19 +0100,

Anthony Jaguenaud <capello@×××××××××.org> a écrit :





> _Il veut pas que je downgrade :-(_
>
> * Messages for package sys-libs/glibc-2.5-r4:
>
>  * Sanity check to keep you from breaking your system:
>  *  Downgrading glibc is not supported and a sure way to destruction
>  *
>  * ERROR: sys-libs/glibc-2.5-r4 failed.
>  * Call stack:
>  *             ebuild.sh, line 1717:  Called dyn_setup
>  *             ebuild.sh, line  768:  Called qa_call 'pkg_setup'
>  *             ebuild.sh, line   44:  Called pkg_setup
>  *   glibc-2.5-r4.ebuild, line 1077:  Called die
>  * The specific snippet of code:
>  *                      die "aborting to save your system"
>  *  The die message:
>  *   aborting to save your system
>  *
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/tmp/portage/sys-libs/glibc-2.5-r4/temp/build.log'.
>  *
>


Aïe ! Je savais pas que l'ebuild protégeait d'un downgrade, désolé :(



Pas vraiment de solution alors de ce coté là :(



> _Pour sandbox, voici les message que j'obtiens :_
> lestat ~ # FEATURES=-sandbox emerge sandbox
> Calculating dependencies... done!
>  >>> Verifying ebuild Manifests...
>
>  >>> Emerging (1 of 1) sys-apps/sandbox-1.2.18.1-r2 to /
>  * sandbox-1.2.18.1.tar.bz2 RMD160 SHA1 SHA256 size ;-)
> ...                                                 [ ok ]
>  * checking ebuild checksums ;-)
> ...
> [ ok ]
>  * checking auxfile checksums ;-)
> ...
> [ ok ]
>  * checking miscfile checksums ;-)
> ...
> [ ok ]
>  * checking sandbox-1.2.18.1.tar.bz2 ;-)
> ...
> [ ok ]
>  >>> Unpacking source...
>  >>> Unpacking sandbox-1.2.18.1.tar.bz2 to
> /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work
>  * Applying sandbox-1.2.18.1-open-normal-fail.patch
> ...                                                     [ ok ]
>  * Applying sandbox-1.2.18.1-open-cloexec.patch
> ...                                                         [ ok ]
>  >>> Source unpacked.
>  >>> Compiling source in
> /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
>  * If configure fails with a 'cannot run C compiled programs' error,
> try this:
>  * FEATURES=-sandbox emerge sandbox
> *!!! Problem with sandbox binary. Disabling.*..
>
>  * Configuring sandbox for ABI=x86...
>  * econf: updating sandbox-1.2.18.1/config.guess with
> /usr/share/gnuconfig/config.guess
>  * econf: updating sandbox-1.2.18.1/config.sub with
> /usr/share/gnuconfig/config.sub
> ../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu
> --mandir=/usr/share/man --infodir=/usr/share/info
> --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib
> --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
> checking for C compiler default output file name... configure: error:
> C compiler cannot create executables
> See `config.log' for more details.
>
> !!! Please attach the following file when filing a report to
> bugs.gentoo.org:
> !!!
> /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
>  *
>  * ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
>  * Call stack:
>  *                    ebuild.sh, line 1701:  Called dyn_compile
>  *                    ebuild.sh, line 1039:  Called qa_call
> 'src_compile'
>  *                    ebuild.sh, line   44:  Called src_compile
>  *   sandbox-1.2.18.1-r2.ebuild, line   87:  Called econf
> '--libdir=/usr/lib32' '--enable-multilib'
>  *                    ebuild.sh, line  638:  Called die
>  * The specific snippet of code:
>  *                      die "econf failed"
>  *  The die message:
>  *   econf failed
>  *
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.
>  *
>
>  * Messages for package sys-apps/sandbox-1.2.18.1-r2:
>
>  *
>  * ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
>  * Call stack:
>  *                    ebuild.sh, line 1701:  Called dyn_compile
>  *                    ebuild.sh, line 1039:  Called qa_call
> 'src_compile'
>  *                    ebuild.sh, line   44:  Called src_compile
>  *   sandbox-1.2.18.1-r2.ebuild, line   87:  Called econf
> '--libdir=/usr/lib32' '--enable-multilib'
>  *                    ebuild.sh, line  638:  Called die
>  * The specific snippet of code:
>  *                      die "econf failed"
>  *  The die message:
>  *   econf failed
>  *
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.
>  *
>  * If configure fails with a 'cannot run C compiled programs' error,
> try this:
>  * *FEATURES=-sandbox emerge sandbox*
>
>
>
> _Voici le fichier de log :
>
> _checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
> checking for C compiler default output file name... configure:
> *error: C compiler cannot create executables*
>


Alors là tu es dans la m... ! ;)

Pour voir, est-ce que gcc --version te sors quelque chose déjà ? Et

quoi ?



Ensuite, ça à l'air d'être la partie 32bits qui pose soucis, est-ce que

ta nouvelle glibc as été compilée pour x86 également ? Quelle version ??



Tu peux voir si les bibliothèques sont présentes dans /lib32/



est-ce que portage te laisserais recompiler gcc et les binutils sans

forcer l'upgrade de sandbox ? Si c'est le cas je ferai ça et après un

reboot ça devrait aller mieux. Croise les doigts !



Sinon autre solution à garder sous le coude : avoir un cd d'install

Gentoo pour booter dessus en cas de catastrophe et te préparer un paquet

stage2 ou 3, je ne sais plus lequel mais comme pour l'installation, pour

écraser le système de base avec quelque chose de fonctionnel. C'est

bourrin mais on peut aussi s'en sortir comme ça ...



Donne nous plus de détails !!



Bonne chance !



Didier



- -- 

Didier Link <didier@××××××××××××.fr>

Jabber : didier_link@××××××.fr

MSN : zanfib@×××××××.fr

SIP : Zanfib@×××××.net



Clé GPG : 75BAC9EE

-----BEGIN PGP SIGNATURE-----

Version: GnuPG v2.0.7 (GNU/Linux)



iD8DBQFHkKPxkyPwinW6ye4RAglSAKCtWFlRswqWU8bLQT20VA3fQgHAhACfSwXP

Rd/FKNU2QfDSHG2f3aMZzC0=

=6OxK

-----END PGP SIGNATURE-----