View previous topic :: View next topic |
Author |
Message |
Neuromancien l33t
Joined: 03 Dec 2003 Posts: 867
|
Posted: Sat Apr 04, 2009 5:56 pm Post subject: [Gcc] error while loading shared libraries (résolu) |
|
|
Bonjour,
Après une mise à jour de Gcc, j'obtiens l'erreur suivante en lançant certains binaires :
Code: | eix: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory |
Le guide de mise à jour de Gcc indique de lancer fix_libtool_files.sh et de réinstaller libtool. Je n'arrive à faire ni l'un ni l'autre :
Code: | checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name...
configure: error: in `/var/tmp/portage/sys-devel/libtool-1.5.26/work/libtool-1.5.26':
configure: error: C compiler cannot create executables
See `config.log' for more details.
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-devel/libtool-1.5.26/work/libtool-1.5.26/config.log
*
* ERROR: sys-devel/libtool-1.5.26 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2191: Called _eapi0_src_compile
* ebuild.sh, line 607: Called econf
* ebuild.sh, line 543: 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-devel/libtool-1.5.26/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-1.5.26/temp/environment'.
* |
_________________ emerge --info
dmesg
lspci
.config
Last edited by Neuromancien on Sun Apr 05, 2009 9:45 am; edited 1 time in total |
|
Back to top |
|
|
titoucha Advocate
Joined: 21 Jul 2005 Posts: 2374 Location: Genève
|
Posted: Sat Apr 04, 2009 6:24 pm Post subject: |
|
|
Que te retourne la commande _________________ Assurez-vous que le titre de votre message soit conforme aux conventions de ce forum (paragraphe 3/3 : Comment poster sur le forum ??) |
|
Back to top |
|
|
Neuromancien l33t
Joined: 03 Dec 2003 Posts: 867
|
Posted: Sat Apr 04, 2009 6:42 pm Post subject: |
|
|
titoucha wrote: | Que te retourne la commande |
Code: | tux jerome # gcc-config -l
* gcc-config: Active gcc profile is invalid!
[1] x86_64-pc-linux-gnu-4.3.2 |
_________________ emerge --info
dmesg
lspci
.config |
|
Back to top |
|
|
kernelsensei Bodhisattva
Joined: 22 Feb 2004 Posts: 5619 Location: Woustviller/Moselle/FRANCE (49.07°N;7.02°E)
|
Posted: Sat Apr 04, 2009 8:41 pm Post subject: |
|
|
Salut,
essaye
_________________ $ ruby -e'puts " .:@BFegiklnorst".unpack("x4ax7aaX6ax5aX15ax4aax6aaX7ax2aX5aX8 \
axaX3ax8aX4ax6aX3aX6ax3ax3aX9ax4ax2aX9axaX6ax3aX2ax4ax3aX4aXaX12ax10aaX7a").join' |
|
Back to top |
|
|
Neuromancien l33t
Joined: 03 Dec 2003 Posts: 867
|
Posted: Sat Apr 04, 2009 9:03 pm Post subject: |
|
|
kernelsensei wrote: | Salut,
essaye
|
Merci. J'avais fini par trouver cette commande sur Internet et repris la mise à jour qui semble bien se passer jusqu'à présent. En fait, c'est indiqué dans le le guide mise à jour de Gcc mais je l'avais lu un peu trop vite... _________________ emerge --info
dmesg
lspci
.config |
|
Back to top |
|
|
|