"Klaus Rudolph" <lts-rudolph@xxxxxx> writes: > Axel Freyn wrote: >> Did you install the development packages? that is, the ubuntu-package >> libc6-dev? >> If not, the compiler is right :) >> If yes -- could you post where on your Ñystem libc.so and libm.so really >> exist? >> > > the packages are installed and running the gcc/g++ compiler which comes with ubuntu runs fine. > > The libs could be found: > > krud@mauersegler:~$ ls -lsa /usr/lib/i386-linux-gnu/libc.so > 4 -rw-r--r-- 1 root root 283 2011-04-11 13:03 /usr/lib/i386-linux-gnu/libc.so > krud@mauersegler:~$ ls -lsa /lib/i386-linux-gnu/libc.so.6 > 0 lrwxrwxrwx 1 root root 12 2011-05-17 14:27 /lib/i386-linux-gnu/libc.so.6 -> libc-2.13.so > krud@mauersegler:~/test/c++/compile_ubuntu_11.04$ ls -lsa /lib/i386-linux-gnu/libc-2.13.so > 1404 -rwxr-xr-x 1 root root 1434180 2011-04-11 13:08 /lib/i386-linux-gnu/libc-2.13.s > > The xgcc is not looking inside /usr/lib/i386-linux-gnu ... > > Is there a trick to setup the compiler build (configure??, environment flags) with some additional lib path infos to give xgcc a chance to find the libs? This is interesting and somewhat annoying. I hope the Ubuntu developers who chose to move these packages will be willing to share patches with gcc so that gcc works by default. It may work if you pass --build=i386-linux-gnu when you configure gcc. Ian
