2 # Last modified: Thu Feb 8 11:38:12 EST 1996
3 # Andy Dougherty <doughera@lafcol.lafayette.edu>
4 # Based on input from lots of folks, especially
5 # Dean Roehrich <roehrich@ironwood-fddi.cray.com>
12 # Avoid all libraries in /usr/ucblib.
13 set `echo $glibpth | sed -e 's@/usr/ucblib@@'`
16 # Remove bad libraries. -lucb contains incompatible routines.
17 # -lld doesn't do anything useful.
18 # -lmalloc can cause a problem with GNU CC & Solaris. Specifically,
19 # libmalloc.a may allocate memory that is only 4 byte aligned, but
20 # GNU CC on the Sparc assumes that doubles are 8 byte aligned.
21 # Thanks to Hallvard B. Furuseth <h.b.furuseth@usit.uio.no>
22 set `echo " $libswanted " | sed -e 's@ ld @ @' -e 's@ malloc @ @' -e 's@ ucb @ @'`
25 # Look for architecture name. We want to suggest a useful default.
28 if test -f /usr/bin/arch; then
29 archname=`/usr/bin/arch`
30 archname="${archname}-${osname}"
31 elif test -f /usr/ucb/arch; then
32 archname=`/usr/ucb/arch`
33 archname="${archname}-${osname}"
38 ######################################################
39 # General sanity testing. See below for excerpts from the Solaris FAQ.
41 # From roehrich@ironwood-fddi.cray.com Wed Sep 27 12:51:46 1995
42 # Date: Thu, 7 Sep 1995 16:31:40 -0500
43 # From: Dean Roehrich <roehrich@ironwood-fddi.cray.com>
44 # To: perl5-porters@africa.nicoh.com
45 # Subject: Re: On perl5/solaris/gcc
47 # Here's another draft of the perl5/solaris/gcc sanity-checker.
50 */usr/ucb*:/usr/bin:*|*/usr/ucb*:/usr/bin) cat <<END
52 NOTE: Some people have reported problems with /usr/ucb/cc.
53 Remove /usr/ucb from your PATH if you have difficulties.
60 # Check that /dev/fd is mounted. If it is not mounted, let the
61 # user know that suid scripts may not work.
62 /usr/bin/df /dev/fd 2>&1 > /dev/null
68 NOTE: Your system does not have /dev/fd mounted. If you want to
69 be able to use set-uid scripts you must ask your system administrator
77 # See if libucb can be found in /usr/lib. If it is, warn the user
78 # that this may cause problems while building Perl extensions.
79 /usr/bin/ls /usr/lib/libucb* >/dev/null 2>&1
84 NOTE: libucb has been found in /usr/lib. libucb should reside in
85 /usr/ucblib. You may have trouble while building Perl extensions.
92 # See if make(1) is GNU make(1).
93 # If it is, make sure the setgid bit is not set.
94 make -v > make.vers 2>&1
95 if grep GNU make.vers > /dev/null 2>&1; then
96 tmp=`/usr/bin/which make`
97 case "`/usr/bin/ls -l $tmp`" in
101 NOTE: Your PATH points to GNU make, and your GNU make has the set-group-id
102 bit set. You must either rearrange your PATH to put /usr/ccs/bin before the
103 GNU utilities or you must ask your system administrator to disable the
104 set-group-id bit on GNU make.
112 # If the C compiler is gcc:
113 # - check the fixed-includes
114 # - check as(1) and ld(1), they should not be GNU
115 # If the C compiler is not gcc:
116 # - check as(1) and ld(1), they should not be GNU
118 # Watch out in case they have not set $cc.
119 case "`${cc:-cc} -v 2>&1`" in
126 # Get gcc to share its secrets.
127 echo 'main() { return 0; }' > try.c
128 verbose=`${cc:-cc} -v -o try try.c 2>&1`
130 tmp=`echo "$verbose" | grep '^Reading' |
131 awk '{print $NF}' | sed 's/specs$/include/'`
133 # Determine if the fixed-includes look like they'll work.
134 # Doesn't work anymore for gcc-2.7.2.
136 # See if as(1) is GNU as(1). GNU as(1) won't work for this job.
138 */usr/ccs/bin/as*) ;;
142 NOTE: You are using GNU as(1). GNU as(1) will not build Perl.
143 You must arrange to use /usr/ccs/bin/as, perhaps by setting
144 GCC_EXEC_PREFIX or by including -B/usr/ccs/bin/ in your cc command.
150 # See if ld(1) is GNU ld(1). GNU ld(1) won't work for this job.
152 */usr/ccs/bin/ld*) ;;
156 NOTE: You are using GNU ld(1). GNU ld(1) will not build Perl.
157 You must arrange to use /usr/ccs/bin/ld, perhaps by setting
158 GCC_EXEC_PREFIX or by including -B/usr/ccs/bin/ in your cc command.
171 # See if as(1) is GNU as(1). GNU as(1) won't work for this job.
172 case `as --version < /dev/null 2>&1` in
176 NOTE: You are using GNU as(1). GNU as(1) will not build Perl.
177 You must arrange to use /usr/ccs/bin, perhaps by adding it to the
178 beginning of your PATH.
184 # See if ld(1) is GNU ld(1). GNU ld(1) won't work for this job.
185 # ld --version doesn't properly report itself as a GNU tool,
186 # as of ld version 2.6, so we need to be more strict. TWP 9/5/96
188 case `ld --version < /dev/null 2>&1` in
189 *GNU*|ld\ version\ 2*)
196 no\ ld\ in*|[Cc]ommand\ not\ found*)
205 NOTE: You are using GNU ld(1). GNU ld(1) will not build Perl.
206 You must arrange to use /usr/ccs/bin, perhaps by adding it to the
207 beginning of your PATH.
215 # as --version or ld --version might dump core.
218 # This is just a trick to include some useful notes.
219 cat > /dev/null <<'End_of_Solaris_Notes'
221 Here are some notes kindly contributed by Dean Roehrich.
224 Generic notes about building Perl5 on Solaris:
225 - Use /usr/ccs/bin/make.
226 - If you use GNU make, remove its setgid bit.
227 - Remove all instances of *ucb* from your path.
228 - Make sure libucb is not in /usr/lib (it should be in /usr/ucblib).
229 - Do not use GNU as or GNU ld, or any of GNU binutils or GNU libc.
230 - Do not use /usr/ucb/cc.
231 - Do not change Configure's default answers, except for the path names.
232 - Do not use -lmalloc.
233 - Do not build on SunOS 4 and expect it to work properly on SunOS 5.
234 - /dev/fd must be mounted if you want set-uid scripts to work.
237 Here are the gcc-related questions and answers from the Solaris 2 FAQ. Note
240 - run fixincludes correctly
241 - don't use GNU as or GNU ld
243 Question 5.7 covers the __builtin_va_alist problem people are always seeing.
244 Question 6.1.3 covers the GNU as and GNU ld issues which are always biting
246 Question 6.9 is for those who are still trying to compile Perl4.
248 The latest Solaris 2 FAQ can be found in the following locations:
249 rtfm.mit.edu:/pub/usenet-by-group/comp.sys.sun.admin
250 ftp.fwi.uva.nl:/pub/solaris
252 Perl5 comes with a script in the top-level directory called "myconfig" which
253 will print a summary of the configuration in your config.sh. My summary for
254 Solaris 2.4 and gcc 2.6.3 follows. I have also built with gcc 2.7.0 and the
255 results are identical. This configuration was generated with Configure's -d
256 option (take all defaults, don't bother prompting me). All tests pass for
259 Summary of my perl5 (patchlevel 1) configuration:
261 osname=solaris, osver=2.4, archname=sun4-solaris
262 uname='sunos poplar 5.4 generic_101945-27 sun4d sparc '
265 cc='gcc', optimize='-O', ld='gcc'
269 stdchar='unsigned char', d_stdstdio=define, usevfork=false
270 voidflags=15, castflags=0, d_casti32=define, d_castneg=define
271 intsize=4, alignbytes=8, usemymalloc=y, randbits=15
274 libpth=/lib /usr/lib /usr/ccs/lib /usr/local/lib
275 libs=-lsocket -lnsl -ldl -lm -lc -lcrypt
276 libc=/usr/lib/libc.so
278 dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef
279 cccdlflags='-fpic', ccdlflags=' ', lddlflags='-G'
288 From: Casper.Dik@Holland.Sun.COM (Casper H.S. Dik - Network Security Engineer)
289 Subject: Solaris 2 Frequently Asked Questions (FAQ) 1.48
290 Date: 25 Jul 1995 12:20:18 GMT
292 5.7) Why do I get __builtin_va_alist or __builtin_va_arg_incr undefined?
294 You're using gcc without properly installing the gcc fixed
295 include files. Or you ran fixincludes after installing gcc
296 w/o moving the gcc supplied varargs.h and stdarg.h files
297 out of the way and moving them back again later. This often
298 happens when people install gcc from a binary distribution.
299 If there's a tmp directory in gcc's include directory, fixincludes
300 didn't complete. You should have run "just-fixinc" instead.
302 Another possible cause is using ``gcc -I/usr/include.''
304 6.1) Where is the C compiler or where can I get one?
310 Gcc is available from the GNU archives in source and binary
311 form. Look in a directory called sparc-sun-solaris2 for
312 binaries. You need gcc 2.3.3 or later. You should not use
313 GNU as or GNU ld. Make sure you run just-fixinc if you use
314 a binary distribution. Better is to get a binary version and
315 use that to bootstrap gcc from source.
319 When you install gcc, don't make the mistake of installing
320 GNU binutils or GNU libc, they are not as capable as their
321 counterparts you get with Solaris 2.x.
323 6.9) I can't get perl 4.036 to compile or run.
325 Run Configure, and use the solaris_2_0 hints, *don't* use
326 the solaris_2_1 hints and don't use the config.sh you may
327 already have. First you must make sure Configure and make
328 don't find /usr/ucb/cc. (It must use gcc or the native C
329 compiler: /opt/SUNWspro/bin/cc)
331 Some questions need a special answer.
333 Are your system (especially dbm) libraries compiled with gcc? [y] y
335 yes: gcc 2.3.3 or later uses the standard calling
336 conventions, same as Sun's C.
338 Any additional cc flags? [ -traditional -Dvolatile=__volatile__
339 -I/usr/ucbinclude] -traditional -Dvolatile=__volatile__
340 Remove /usr/ucbinclude.
342 Any additional libraries? [-lsocket -lnsl -ldbm -lmalloc -lm
343 -lucb] -lsocket -lnsl -lm
345 Don't include -ldbm, -lmalloc and -lucb.
347 Perl 5 compiled out of the box.