Prb -lc with pike 7.0.78 on UnixWare 7.X.X and OpenServer 5.0.X
Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=397
Reported by @grubba
From: Boyd Lynn Gerber <email@example.com> To: firstname.lastname@example.org Date: Sat, 23 Sep 2000 12:08:16 -0600 (MDT) Subject: Prb -lc with pike 7.0.78 on UnixWare 7.X.X and OpenServer 5.0.X
To whom it may concern:
I have found this problem with both SCO OS's. The compilers add the libc where needed. How do I prevent pike builds using the -lc option.
I have been having some strange behavoir with Roxen and Caudium on UnixWare 7.X.X and OpenServer. If I run the make check on UnixWare 7.X.X, I get different things on each build and make check. I can get a core dump a race condition consuming resources The load jumps to over 30.
I was using gdb tracing things and found shared libs were jumping to locations that were bogus. It was going to the same place that gmp-3.1 goes when .so are compiled with the -lc option. I have traced it to build .so files with the -lc option. I then downloaded the latest stable pike and used the SCO UDK cc compiler instead of gcc. gcc does not give any warnings about the -lc, although they both automatically link in libc where needed. I found that pike .so's are all being made with the -lc option. This warning from the SCO UDK cc should not be over looked.
UX:cc: WARNING: Avoid specifying -lc; cc will ensure that libc is linked in the proper order. Linking libc in the wrong order may cause incorrect execution behavior. If you do specify -lc, make sure that no dynamic libraries are specified after it.
I can not find where the -lc is being added. It appears the Makefiles do not have it, but I see the complaint with the SCO UDK compiler. I am not sure how to fix it.
-- Boyd Gerber email@example.com ZENEZ 3748 Valley Forge Road, Magna Utah 84044 Office 801-250-0795 FAX 801-250-7975