2 # Last modified: Tue Apr 13 13:12:49 EDT 1999
3 # Andy Dougherty <doughera@lafayette.edu>
4 # Based on input from lots of folks, especially
5 # Dean Roehrich <roehrich@ironwood-fddi.cray.com>
7 # If perl fails tests that involve dynamic loading of extensions, and
8 # you are using gcc, be sure that you are NOT using GNU as and ld. One
9 # way to do that is to invoke Configure with
11 # sh Configure -Dcc='gcc -B/usr/ccs/bin/'
13 # (Note that the trailing slash is *required*.)
14 # gcc will occasionally emit warnings about "unused prefix", but
15 # these ought to be harmless. See below for more details.
22 # Avoid all libraries in /usr/ucblib.
23 set `echo $glibpth | sed -e 's@/usr/ucblib@@'`
26 # Remove bad libraries. -lucb contains incompatible routines.
27 # -lld doesn't do anything useful.
28 # -lmalloc can cause a problem with GNU CC & Solaris. Specifically,
29 # libmalloc.a may allocate memory that is only 4 byte aligned, but
30 # GNU CC on the Sparc assumes that doubles are 8 byte aligned.
31 # Thanks to Hallvard B. Furuseth <h.b.furuseth@usit.uio.no>
32 set `echo " $libswanted " | sed -e 's@ ld @ @' -e 's@ malloc @ @' -e 's@ ucb @ @'`
35 # Look for architecture name. We want to suggest a useful default.
38 if test -f /usr/bin/arch; then
39 archname=`/usr/bin/arch`
40 archname="${archname}-${osname}"
41 elif test -f /usr/ucb/arch; then
42 archname=`/usr/ucb/arch`
43 archname="${archname}-${osname}"
48 ######################################################
49 # General sanity testing. See below for excerpts from the Solaris FAQ.
51 # From roehrich@ironwood-fddi.cray.com Wed Sep 27 12:51:46 1995
52 # Date: Thu, 7 Sep 1995 16:31:40 -0500
53 # From: Dean Roehrich <roehrich@ironwood-fddi.cray.com>
54 # To: perl5-porters@africa.nicoh.com
55 # Subject: Re: On perl5/solaris/gcc
57 # Here's another draft of the perl5/solaris/gcc sanity-checker.
59 test -z "`${cc:-cc} -V 2>/dev/null|grep -i workshop`" || ccisworkshop="$define"
60 test -z "`${cc:-cc} -v 2>/dev/null|grep -i gcc`" || ccisgcc="$define"
62 case "$ccisworkshop" in
66 int main() { return(0); }
68 workshoplibs=`cc -### try.c -lsunmath -o try 2>&1|grep " -Y "|sed 's%.* -Y "P,\(.*\)".*%\1%'|tr ':' '\n'|grep '/SUNWspro/'|sort -u`
69 loclibpth="$loclibpth $workshoplibs"
73 case `type ${cc:-cc}` in
74 */usr/ucb/cc*) cat <<END >&4
76 NOTE: Some people have reported problems with /usr/ucb/cc.
77 If you have difficulties, please make sure the directory
78 containing your C compiler is before /usr/ucb in your PATH.
85 # Check that /dev/fd is mounted. If it is not mounted, let the
86 # user know that suid scripts may not work.
87 /usr/bin/df /dev/fd 2>&1 > /dev/null
93 NOTE: Your system does not have /dev/fd mounted. If you want to
94 be able to use set-uid scripts you must ask your system administrator
102 # See if libucb can be found in /usr/lib. If it is, warn the user
103 # that this may cause problems while building Perl extensions.
104 /usr/bin/ls /usr/lib/libucb* >/dev/null 2>&1
109 NOTE: libucb has been found in /usr/lib. libucb should reside in
110 /usr/ucblib. You may have trouble while building Perl extensions.
116 # Use shell built-in 'type' command instead of /usr/bin/which to
117 # avoid possible csh start-up problems and also to use the same shell
118 # we'll be using to Configure and make perl.
119 # The path name is the last field in the output, but the type command
120 # has an annoying array of possible outputs, e.g.:
121 # make is hashed (/opt/gnu/bin/make)
124 # use a command like type make | awk '{print $NF}' | sed 's/[()]//g'
126 # See if make(1) is GNU make(1).
127 # If it is, make sure the setgid bit is not set.
128 make -v > make.vers 2>&1
129 if grep GNU make.vers > /dev/null 2>&1; then
130 tmp=`type make | awk '{print $NF}' | sed 's/[()]//g'`
131 case "`/usr/bin/ls -lL $tmp`" in
135 NOTE: Your PATH points to GNU make, and your GNU make has the set-group-id
136 bit set. You must either rearrange your PATH to put /usr/ccs/bin before the
137 GNU utilities or you must ask your system administrator to disable the
138 set-group-id bit on GNU make.
146 # XXX EXPERIMENTAL A.D. 2/27/1998
147 # XXX This script UU/cc.cbu will get 'called-back' by Configure after it
148 # XXX has prompted the user for the C compiler to use.
149 cat > UU/cc.cbu <<'EOSH'
150 # If the C compiler is gcc:
151 # - check the fixed-includes
152 # - check as(1) and ld(1), they should not be GNU
153 # (GNU as and ld 2.8.1 and later are reportedly ok, however.)
154 # If the C compiler is not gcc:
155 # - check as(1) and ld(1), they should not be GNU
156 # (GNU as and ld 2.8.1 and later are reportedly ok, however.)
158 # Watch out in case they have not set $cc.
160 # Perl compiled with some combinations of GNU as and ld may not
161 # be able to perform dynamic loading of extensions. If you have a
162 # problem with dynamic loading, be sure that you are using the Solaris
163 # /usr/ccs/bin/as and /usr/ccs/bin/ld. You can do that with
164 # sh Configure -Dcc='gcc -B/usr/ccs/bin/'
165 # (note the trailing slash is required).
166 # Combinations that are known to work with the following hints:
168 # gcc-2.7.2, GNU as 2.7, GNU ld 2.7
169 # egcs-1.0.3, GNU as 2.9.1 and GNU ld 2.9.1
170 # --Andy Dougherty <doughera@lafayette.edu>
171 # Tue Apr 13 17:19:43 EDT 1999
173 # Get gcc to share its secrets.
174 echo 'main() { return 0; }' > try.c
175 # Indent to avoid propagation to config.sh
176 verbose=`${cc:-cc} -v -o try try.c 2>&1`
178 if echo "$verbose" | grep '^Reading specs from' >/dev/null 2>&1; then
183 tmp=`echo "$verbose" | grep '^Reading' |
184 awk '{print $NF}' | sed 's/specs$/include/'`
186 # Determine if the fixed-includes look like they'll work.
187 # Doesn't work anymore for gcc-2.7.2.
189 # See if as(1) is GNU as(1). GNU as(1) might not work for this job.
190 if echo "$verbose" | grep ' /usr/ccs/bin/as ' >/dev/null 2>&1; then
195 NOTE: You are using GNU as(1). GNU as(1) might not build Perl. If you
196 have trouble, you can use /usr/ccs/bin/as by including -B/usr/ccs/bin/
197 in your ${cc:-cc} command. (Note that the trailing "/" is required.)
200 # Apparently not needed, at least for as 2.7 and later.
201 # cc="${cc:-cc} -B/usr/ccs/bin/"
204 # See if ld(1) is GNU ld(1). GNU ld(1) might not work for this job.
205 # Recompute $verbose since we may have just changed $cc.
206 verbose=`${cc:-cc} -v -o try try.c 2>&1 | grep ld 2>&1`
208 if echo "$verbose" | grep ' /usr/ccs/bin/ld ' >/dev/null 2>&1; then
209 # Ok, gcc directly calls the Solaris /usr/ccs/bin/ld.
211 elif echo "$verbose" | grep "ld: Software Generation Utilities" >/dev/null 2>&1; then
212 # Hmm. gcc doesn't call /usr/ccs/bin/ld directly, but it
213 # does appear to be using it eventually. egcs-1.0.3's ld
215 # All Solaris versions of ld I've seen contain the magic
216 # string used in the grep.
219 # No evidence yet of /usr/ccs/bin/ld. Some versions
220 # of egcs's ld wrapper call /usr/ccs/bin/ld in turn but
221 # apparently don't reveal that unless you pass in -V.
222 # (This may all depend on local configurations too.)
224 myld=`echo $verbose| grep ld | awk '/\/ld/ {print $1}'`
225 # This assumes that gcc's output will not change, and that
226 # /full/path/to/ld will be the first word of the output.
227 # Thus myld is something like opt/gnu/sparc-sun-solaris2.5/bin/ld
229 if $myld -V 2>&1 | grep "ld: Software Generation Utilities" >/dev/null 2>&1; then
230 # Ok, /usr/ccs/bin/ld eventually does get called.
235 NOTE: You are using GNU ld(1). GNU ld(1) might not build Perl. If you
236 have trouble, you can use /usr/ccs/bin/ld by including -B/usr/ccs/bin/
237 in your ${cc:-cc} command. (Note that the trailing "/" is required.)
239 I will try to use GNU ld by passing in the -Wl,-E flag, but if that
240 doesn't work, you should use -B/usr/ccs/bin/ instead.
243 ccdlflags="$ccdlflags -Wl,-E"
244 lddlflags="$lddlflags -W,l-E -G"
253 # See if as(1) is GNU as(1). GNU might not work for this job.
254 case `as --version < /dev/null 2>&1` in
258 NOTE: You are using GNU as(1). GNU as(1) might not build Perl.
259 You must arrange to use /usr/ccs/bin/as, perhaps by adding /usr/ccs/bin
260 to the beginning of your PATH.
266 # See if ld(1) is GNU ld(1). GNU ld(1) might not work for this job.
267 # ld --version doesn't properly report itself as a GNU tool,
268 # as of ld version 2.6, so we need to be more strict. TWP 9/5/96
270 case `ld --version < /dev/null 2>&1` in
271 *GNU*|ld\ version\ 2*)
277 # Try to guess from path
278 case `type ld | awk '{print $NF}'` in
286 NOTE: You are apparently using GNU ld(1). GNU ld(1) might not build Perl.
287 You should arrange to use /usr/ccs/bin/ld, perhaps by adding /usr/ccs/bin
288 to the beginning of your PATH.
295 # as --version or ld --version might dump core.
302 cat > UU/usethreads.cbu <<'EOCBU'
303 # This script UU/usethreads.cbu will get 'called-back' by Configure
304 # after it has prompted the user for whether to use threads.
305 case "$usethreads" in
307 ccflags="-D_REENTRANT $ccflags"
309 # sched_yield is in -lposix4
310 set `echo X "$libswanted "| sed -e 's/ c / posix4 pthread c /'`
314 # On Solaris 2.6 x86 there is a bug with sigsetjmp() and siglongjmp()
315 # when linked with the threads library, such that whatever positive
316 # value you pass to siglongjmp(), sigsetjmp() returns 1.
317 # Thanks to Simon Parsons <S.Parsons@ftel.co.uk> for this report.
318 # Sun BugID is 4117946, "sigsetjmp always returns 1 when called by
319 # siglongjmp in a MT program". As of 19980622, there is no patch
322 /* Test for sig(set|long)jmp bug. */
330 ret = sigsetjmp(env, 1);
331 if (ret) { return ret == 2; }
335 if test "`arch`" = i86pc -a "$osvers" = 2.6 && \
336 ${cc:-cc} try.c -lpthread >/dev/null 2>&1 && ./a.out; then
340 You will see a *** WHOA THERE!!! *** message from Configure for
341 d_sigsetjmp. Keep the recommended value. See hints/solaris_2.sh
342 for more information.
350 cat > UU/uselargefiles.cbu <<'EOCBU'
351 # This script UU/uselargefiles.cbu will get 'called-back' by Configure
352 # after it has prompted the user for whether to use large files.
353 case "$uselargefiles" in
354 ''|$define|true|[yY]*)
355 ccflags="$ccflags `getconf LFS_CFLAGS 2>/dev/null`"
356 ldflags="$ldflags `getconf LFS_LDFLAGS 2>/dev/null`"
357 libswanted="$libswanted `getconf LFS_LIBS 2>/dev/null|sed -e 's@^-l@@' -e 's@ -l@ @g`"
362 cat > UU/use64bitint.cbu <<'EOCBU'
363 # This script UU/use64bitint.cbu will get 'called-back' by Configure
364 # after it has prompted the user for whether to use 64 bit integers.
365 case "$use64bitint" in
366 "$define"|true|[yY]*)
370 Solaris `uname -r` does not support 64-bit integers.
371 You should upgrade to at least Solaris 2.7.
380 cat > UU/use64bitall.cbu <<'EOCBU'
381 # This script UU/use64bitall.cbu will get 'called-back' by Configure
382 # after it has prompted the user for whether to be maximally 64 bitty.
383 case "$use64bitall" in
384 "$define"|true|[yY]*)
385 libc='/usr/lib/sparcv9/libc.so'
386 if test ! -f $libc; then
389 I do not see the 64-bit libc, $libc.
390 Cannot continue, aborting.
395 loclibpth="$loclibpth /usr/lib/sparcv9"
396 case "$cc -v 2>/dev/null" in
398 echo 'main() { return 0; }' > try.c
399 if ${cc:-cc} -mcpu=v9 -m64 -S try.c 2>&1 | grep -e \
400 '-m64 is not supported by this configuration'; then
403 Full 64-bit build not supported by this configuration.
404 Cannot continue, aborting.
409 ccflags="$ccflags -mcpu=v9 -m64"
410 if test X`getconf XBS5_LP64_OFF64_CFLAGS 2>/dev/null` != X; then
411 ccflags="$ccflags -Wa,`getconf XBS5_LP64_OFF64_CFLAGS 2>/dev/null`"
413 # no changes to ld flags, as (according to man ld):
415 # There is no specific option that tells ld to link 64-bit
416 # objects; the class of the first object that gets processed
417 # by ld determines whether it is to perform a 32-bit or a
421 ccflags="$ccflags `getconf XBS5_LP64_OFF64_CFLAGS 2>/dev/null`"
422 ldflags="$ldflags `getconf XBS5_LP64_OFF64_LDFLAGS 2>/dev/null`"
423 lddlflags="$lddlflags -G `getconf XBS5_LP64_OFF64_LDFLAGS 2>/dev/null`"
426 libscheck='case "`/usr/bin/file $xxx`" in
427 *64-bit*|*SPARCV9*) ;;
428 *) xxx=/no/64-bit$xxx ;;
434 # Actually, we want to run this already now, if so requested,
435 # because we need to fix up the flags right now.
436 case "$use64bitall" in
437 "$define"|true|[yY]*)
438 . ./UU/use64bitall.cbu
442 cat > UU/uselongdouble.cbu <<'EOCBU'
443 # This script UU/uselongdouble.cbu will get 'called-back' by Configure
444 # after it has prompted the user for whether to use long doubles.
445 case "$uselongdouble" in
446 "$define"|true|[yY]*)
447 case "$ccisworkshop" in
451 I do not see the libsunmath.so; therefore I cannot do long doubles, sorry.
457 libswanted="$libswanted sunmath"
458 loclibpth="$loclibpth /opt/SUNWspro/lib"
463 rm -f try.c try.o try
464 # keep that leading tab
468 # This is just a trick to include some useful notes.
469 cat > /dev/null <<'End_of_Solaris_Notes'
471 Here are some notes kindly contributed by Dean Roehrich.
474 Generic notes about building Perl5 on Solaris:
475 - Use /usr/ccs/bin/make.
476 - If you use GNU make, remove its setgid bit.
477 - Remove all instances of *ucb* from your path.
478 - Make sure libucb is not in /usr/lib (it should be in /usr/ucblib).
479 - Do not use GNU as or GNU ld, or any of GNU binutils or GNU libc.
480 - Do not use /usr/ucb/cc.
481 - Do not change Configure's default answers, except for the path names.
482 - Do not use -lmalloc.
483 - Do not build on SunOS 4 and expect it to work properly on SunOS 5.
484 - /dev/fd must be mounted if you want set-uid scripts to work.
487 Here are the gcc-related questions and answers from the Solaris 2 FAQ. Note
490 - run fixincludes correctly
491 - don't use GNU as or GNU ld
493 Question 5.7 covers the __builtin_va_alist problem people are always seeing.
494 Question 6.1.3 covers the GNU as and GNU ld issues which are always biting
496 Question 6.9 is for those who are still trying to compile Perl4.
498 The latest Solaris 2 FAQ can be found in the following locations:
499 rtfm.mit.edu:/pub/usenet-by-group/comp.sys.sun.admin
500 ftp.fwi.uva.nl:/pub/solaris
502 Perl5 comes with a script in the top-level directory called "myconfig" which
503 will print a summary of the configuration in your config.sh. My summary for
504 Solaris 2.4 and gcc 2.6.3 follows. I have also built with gcc 2.7.0 and the
505 results are identical. This configuration was generated with Configure's -d
506 option (take all defaults, don't bother prompting me). All tests pass for
509 Summary of my perl5 (patchlevel 1) configuration:
511 osname=solaris, osver=2.4, archname=sun4-solaris
512 uname='sunos poplar 5.4 generic_101945-27 sun4d sparc '
515 cc='gcc', optimize='-O', ld='gcc'
519 stdchar='unsigned char', d_stdstdio=define, usevfork=false
520 voidflags=15, castflags=0, d_casti32=define, d_castneg=define
521 intsize=4, alignbytes=8, usemymalloc=y, randbits=15
524 libpth=/lib /usr/lib /usr/ccs/lib /usr/local/lib
525 libs=-lsocket -lnsl -ldl -lm -lc -lcrypt
526 libc=/usr/lib/libc.so
528 dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef
529 cccdlflags='-fpic', ccdlflags=' ', lddlflags='-G'
538 From: Casper.Dik@Holland.Sun.COM (Casper H.S. Dik - Network Security Engineer)
539 Subject: Solaris 2 Frequently Asked Questions (FAQ) 1.48
540 Date: 25 Jul 1995 12:20:18 GMT
542 5.7) Why do I get __builtin_va_alist or __builtin_va_arg_incr undefined?
544 You're using gcc without properly installing the gcc fixed
545 include files. Or you ran fixincludes after installing gcc
546 w/o moving the gcc supplied varargs.h and stdarg.h files
547 out of the way and moving them back again later. This often
548 happens when people install gcc from a binary distribution.
549 If there's a tmp directory in gcc's include directory, fixincludes
550 didn't complete. You should have run "just-fixinc" instead.
552 Another possible cause is using ``gcc -I/usr/include.''
554 6.1) Where is the C compiler or where can I get one?
560 Gcc is available from the GNU archives in source and binary
561 form. Look in a directory called sparc-sun-solaris2 for
562 binaries. You need gcc 2.3.3 or later. You should not use
563 GNU as or GNU ld. Make sure you run just-fixinc if you use
564 a binary distribution. Better is to get a binary version and
565 use that to bootstrap gcc from source.
569 When you install gcc, don't make the mistake of installing
570 GNU binutils or GNU libc, they are not as capable as their
571 counterparts you get with Solaris 2.x.
573 6.9) I can't get perl 4.036 to compile or run.
575 Run Configure, and use the solaris_2_0 hints, *don't* use
576 the solaris_2_1 hints and don't use the config.sh you may
577 already have. First you must make sure Configure and make
578 don't find /usr/ucb/cc. (It must use gcc or the native C
579 compiler: /opt/SUNWspro/bin/cc)
581 Some questions need a special answer.
583 Are your system (especially dbm) libraries compiled with gcc? [y] y
585 yes: gcc 2.3.3 or later uses the standard calling
586 conventions, same as Sun's C.
588 Any additional cc flags? [ -traditional -Dvolatile=__volatile__
589 -I/usr/ucbinclude] -traditional -Dvolatile=__volatile__
590 Remove /usr/ucbinclude.
592 Any additional libraries? [-lsocket -lnsl -ldbm -lmalloc -lm
593 -lucb] -lsocket -lnsl -lm
595 Don't include -ldbm, -lmalloc and -lucb.
597 Perl 5 compiled out of the box.
599 7.0) 64-bitness, from Alan Burlison (added by jhi 2000-02-21)
601 You need a machine running Solaris 2.7 or above.
605 1. Solaris 2.7 and above will run in either 32 bit or 64 bit mode,
607 2. You can build 64 bit apps whilst running 32 bit mode and vice-versa.
608 3. 32 bit apps will run under Solaris running in either 32 or 64 bit mode.
609 4. 64 bit apps require Solaris to be running 64 bit mode
610 5. It is possible to select the appropriate 32 or 64 bit version of an
611 app at run-time using isaexec(3).
612 6. You can detect the OS mode using "isainfo -v", e.g.
613 fubar$ isainfo -v # Ultra 30 in 64 bit mode
614 64-bit sparcv9 applications
615 32-bit sparc applications
616 7. To compile 64 bit you need to use the flag "-xarch=v9".
617 getconf(1) will tell you this, e.g.
618 fubar$ getconf -a | grep v9
619 XBS5_LP64_OFF64_CFLAGS: -xarch=v9
620 XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
621 XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
622 XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
623 XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
624 XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
625 _XBS5_LP64_OFF64_CFLAGS: -xarch=v9
626 _XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
627 _XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
628 _XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
629 _XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
630 _XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
632 > > Now, what should we do, then? Should -Duse64bits in a v9 box cause
633 > > Perl to compiled in v9 mode? Or should we for compatibility stick
634 > > with 32 bit builds and let the people in the know to add the -xarch=v9
635 > > to ccflags (and ldflags?)?
637 > I think the second (explicit) mechanism should be the default. Unless
638 > you want to allocate more than ~ 4Gb of memory inside Perl, you don't
639 > need Perl to be a 64-bit app. Put it this way, on a machine running
640 > Solaris 8, there are 463 executables under /usr/bin, but only 15 of
641 > those require 64 bit versions - mainly because they invade the kernel
642 > address space, e.g. adb, kgmon etc. Certainly we don't recommend users
643 > to build 64 bit apps unless they need the address space.