Python on UnixWare

Thomas Freeman (tfreeman@netcom.com)
Mon, 25 Jul 1994 22:48:03 GMT

Hello,

I have the following problem when building Python on Novell's
UnixWare 1.1.1, and I hope someone out there can help me.
(UnixWare is Novell's SVR4.2 Unix).

When I do:
CC=/usr/bin/cc ; export CC
./configure -v --with-svr4

It decides that it doesn't like the "socket" library, because
of the following undefined symbols:

>checking for -lsocket
>Undefined first referenced
> symbol in file
>netdir_free /usr/lib/libsocket.so
>netdir_getbyname /usr/lib/libsocket.so
>getnetconfigent /usr/lib/libsocket.so
>getnetconfig /usr/lib/libsocket.so
>freenetconfigent /usr/lib/libsocket.so
>inet_ntoa /usr/lib/libsocket.so
>netdir_getbyaddr /usr/lib/libsocket.so
>gethostname /usr/lib/libsocket.so
>endnetconfig /usr/lib/libsocket.so
>setnetconfig /usr/lib/libsocket.so
>getdomainname /usr/lib/libsocket.so
>UX:ld: ERROR: conftest: fatal error: Symbol referencing errors.
>No output written to conftest

When I then run "make", everything compiles OK, but it
bombs when it is doing the final link of "python".

I edited the Modules/Makefile, and changed the line:

LIBS = -ldl -lsnl

to

LIBS = -ldl -lsocket -lsnl

After this change, the final link works, and "python" then
goes on to pass the "make test".

Question: This can't be the right way to fix this problem.
Is there a better fix (i.e. to "configure")?

P.S. I am using the Novell SDK, compiling as "root",
If I use the "bsd compatibility" mode, it bombs when compiling:
Modules/posixmodule.c
When I use gcc (vers. 2.4.5), I have the same socket linking problem.

Thanks for any help.

-Tom Freeman