1 # Sequent Dynix/Ptx v. 4 hints
2 # Created 1996/03/15 by Brad Howerter, bhower@wgc.woodward.com
4 # Modified 1998/11/10 by Martin J. Bligh, mbligh@sequent.com
5 # to incorporate work done by Kurtis D. Rader & myself.
7 # Use Configure -Dcc=gcc to use gcc.
9 # cc wants -G for dynamic loading
12 # Remove inet to avoid this error in Configure, which causes Configure
13 # to be unable to figure out return types:
14 # dynamic linker: ./ssize: can't find libinet.so,
15 # link with -lsocket instead of -linet
17 libswanted=`echo $libswanted | sed -e 's/ inet / /'`
19 # Configure defaults to usenm='y', which doesn't work very well
22 # removed d_vfork='define'; we can't use it any more ...
25 '') optimize='-Wc,-O3 -W0,-xstring' ;;
28 # We override d_socket because it's very hard for Configure to get it right
29 # in Dynix/Ptx, for several reasons.
30 # (1) the socket interface is in libsocket.so -- this wouldn't be so hard
31 # for Configure to fathom...but it gets more tangled.
32 # (2) if the system has been patched there can be libsocket.so.1.FOO.BAR,
33 # the FOO.BAR being the old version of the system before the patching.
34 # Configure picks up the old broken version.
35 # (3) libsocket.so points to either libsocket.so.1 (v4.2)
36 # or libsocket.so.1.1 (v4.4) The socket call in libsocket.so.1.1
37 # (BSD socket library) is called bsd_socket(), and has a macro wrapper
39 # This information kindly provided by Martin J. Bligh of Sequent.
41 # "Sequent has unusual capabilities, taking it above and beyond
42 # the complexity of any other vendor" :-)
44 # Jarkko Hietaniemi November 1998
47 4.[45]*) # configure doesn't find sockets, as they're in libsocket, not libc
52 4.2*) # on ptx/TCP 4.2, we can use BSD sockets, but they're not the default.
53 cppflags="$cppflags -Wc,+bsd-socket"
54 ccflags="$ccflags -Wc,+bsd-socket"
55 ldflags="$ldflags -Wc,+bsd-socket"