Actually, I just realized that the problem is obvious. The path /usr/lib/gcc/ppc64-redhat-linux/4.3.0/../../../libc.so really refers to /usr/lib - and that's the place for 32-bit libraries. It should instead point to /usr/lib64/gcc/ppc64-redhat-linux/4.3.0/../../../libc.so. So the question really is how to "convince" the linker to go to /usr/lib64 and not to /usr/lib. I'll look into that tomorrow. Time to go home. :-)
Misha "Misha Vodsedalek" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > "Michael Jerris" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] >>> Here is the output: >>> /usr/bin/ld: skipping incompatible >>> /usr/lib/gcc/ppc64-redhat-linux/4.3.0/../../../libc.so when searching >>> for -lc >>> /usr/bin/ld: skipping incompatible >>> /usr/lib/gcc/ppc64-redhat-linux/4.3.0/../../../libc.a when searching >>> for -lc >>> /usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching >>> for -lc >>> /usr/bin/ld: skipping incompatible /usr/lib/libc.a when searching >>> for -lc >>> /usr/bin/ld: cannot find -lc >> >> I think this one is the key. Are you trying to link c++ using gcc as >> the linker? Where in the build is this? in FreeSWITCH or elsewhere >> in sipX? >> > > The build fails for all C++ components. I tried building several of > them - freeswitch, cgicc. The problem is not really an attempt to compile > and link the actual component using gcc - the problem is in the configure > step in which the default output file name is checked. During this check, > configure attempts to compile/link some C++ program using cc (which really > is gcc) to figure out what the default output file name is. This check > fails - configure aborts and I never get to any compilation of sources > that belong to the actual components. > > Misha > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
