So I am using CentOS 6.3 a fresh install and I was trying to add things to my path for OpenMPI so I edited my .bash_profile file to read:
FOO='test'
export FOO
# Add support for MPI
PATH=$PATH:/usr/lib64/openmpi/bin
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
Which apparently isn't being read when I start up a bash shell, my $PATH is without the /usr
gcc 4.6.1 -> 4.8 snapshot
libgomp & libstdc++ v3 didn't compiled on my computer, few times.
$ readelf -l a.out
then eventually i found i have no /lib64, (i have /usr/lib64 symlink).
# ln -s /lib /lib64
then tada!! it works! heh
In a misguided attempt to recompile ld with debug symbols, I ended up with a /lib64 that was not symlinked to /lib (Debian 64-bit libs are in in /lib/x84_64-linux-gnu).
I need to build an apache httpd server that will be able to run under multiple linux os (RH, SUSE, e.t.c.)
The main problem is that httpd is using shared libraries:
ldd httpd/bin/httpd
linux-vdso.so.1 => (0x00007fff955fe000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fec3df54000)
librt.so.1 => /lib64/librt.so.1 (0x00007fec3dd4c000)
libcrypt.so.1 => /lib64/libcrypt
How can I fix this problem? What is libzypp.so.1106 and and libaugeas.so.0?
If I build python with "./configure --prefix=/opt/python2.7/Python-2.7.3 --enable-shared"
I get an executable with the following libraries required by the executable:
# ldd /opt/python2.7/Python-2.7.3/bin/python2.7
libpython2.7.so.1.0 => not found
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003f6ac00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003ec6e00000)
libutil.so
I used gdb to attach to a process. I am trying to figure out why it's stuck in an infinite loop, and what it's doing.
When i try to run umount I got a warning message:
/lib64/libuuid.so.1: no version information available (required by /lib64/libblkid.so.1)
How to correct this ?
I use CentOS 5.8 64-bit.
cfr wrote:falconindy wrote:Arch doesn't use /lib64.$ ls /lib64
ld-2.15.so@ ld-linux-x86-64.so.2@Now go compare that to a distro like Fedora or Ubuntu. The only reason those symlinks exist are for third party binary blobs where the interpreter is /lib64/ld-linux-x86-64.so.2. Rather than change the hardcoded interpreter, we add the symlinks.
Email this page