Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 130252 - ifort asks for libstdc++.so.5
Summary: ifort asks for libstdc++.so.5
Status: RESOLVED DUPLICATE of bug 117452
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-17 05:55 UTC by JDB
Modified: 2006-04-17 07:17 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JDB 2006-04-17 05:55:38 UTC
I installed the intel fortran compiler, downloading the 9.0.031 version and editing the ifc-9.0.026.ebuild. When I execute ifort testing it i get this error:

xeon samples # ifort int_sin.f90
/opt/intel/fortran90/bin/fortcom: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
compilation aborted for int_sin.f90 (code 127)

but libstdc++.so.5 is in my system:

xeon samples # locate libstdc++.so.5
/usr/lib64/libstdc++-v3/libstdc++.so.5
/usr/lib64/libstdc++-v3/libstdc++.so.5.0.6

All the story is at : http://forums.gentoo.org/viewtopic-t-450049.html

Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r7 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r7 x86_64 Intel(R) Xeon(TM) CPU 3.00GHz
Gentoo Base System version 1.6.14
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=nocona"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe -march=nocona"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://168.96.76.51/gentoo-portage"
USE="amd64 alsa apache2 avi berkdb bitmap-fonts bzip2 cli crypt ctype cups dba dri eds emboss encode expat fastbuild foomaticdb force-cgi-redirect fortran ftp gd gif gpm gstreamer gtk2 imlib ipv6 isdnlog jpeg lzw lzw-tiff memlimit mp3 mpeg ncurses nls nptl opengl pam pcre pdflib perl png posix pppd python quicktime readline sdl session simplexml soap sockets spell spl ssl tcpd tiff tokenizer truetype truetype-fonts type1-fonts udev usb xml xpm xsl xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-04-17 06:19:56 UTC

*** This bug has been marked as a duplicate of 117452 ***
Comment 2 JDB 2006-04-17 07:12:57 UTC
ok, but why is this a duplicate? I installed succesfully ifc 031 but testing ifc i get:

xeon ifc # ifort /opt/intel/fortran90/doc/samples/int_sin.f90
/opt/intel/fortran90/bin/fortcom: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
compilation aborted for /opt/intel/fortran90/doc/samples/int_sin.f90 (code 127)
xeon ifc # ldconfig -p | grep libstdc++.so.5
        libstdc++.so.5 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.5/libstdc++.so.5
        libstdc++.so.5 (libc6,x86-64) => /usr/lib64/libstdc++-v3/libstdc++.so.5

Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-04-17 07:17:14 UTC
(In reply to comment #2)
> ok, but why is this a duplicate? I installed succesfully ifc 031 but testing
> ifc i get:

Yeah, so please note it on the other bug, so that it can be fixed before the ebuild gets into portage. We can't fix ebuilds that are not in portage yet. :=)