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 case `type ${cc:-cc}` in
60 */usr/ucb/cc*) cat <<END >&4
62 NOTE: Some people have reported problems with /usr/ucb/cc.
63 If you have difficulties, please make sure the directory
64 containing your C compiler is before /usr/ucb in your PATH.
71 # Check that /dev/fd is mounted. If it is not mounted, let the
72 # user know that suid scripts may not work.
73 /usr/bin/df /dev/fd 2>&1 > /dev/null
79 NOTE: Your system does not have /dev/fd mounted. If you want to
80 be able to use set-uid scripts you must ask your system administrator
88 # See if libucb can be found in /usr/lib. If it is, warn the user
89 # that this may cause problems while building Perl extensions.
90 /usr/bin/ls /usr/lib/libucb* >/dev/null 2>&1
95 NOTE: libucb has been found in /usr/lib. libucb should reside in
96 /usr/ucblib. You may have trouble while building Perl extensions.
102 # Use shell built-in 'type' command instead of /usr/bin/which to
103 # avoid possible csh start-up problems and also to use the same shell
104 # we'll be using to Configure and make perl.
105 # The path name is the last field in the output, but the type command
106 # has an annoying array of possible outputs, e.g.:
107 # make is hashed (/opt/gnu/bin/make)
110 # use a command like type make | awk '{print $NF}' | sed 's/[()]//g'
112 # See if make(1) is GNU make(1).
113 # If it is, make sure the setgid bit is not set.
114 make -v > make.vers 2>&1
115 if grep GNU make.vers > /dev/null 2>&1; then
116 tmp=`type make | awk '{print $NF}' | sed 's/[()]//g'`
117 case "`/usr/bin/ls -lL $tmp`" in
121 NOTE: Your PATH points to GNU make, and your GNU make has the set-group-id
122 bit set. You must either rearrange your PATH to put /usr/ccs/bin before the
123 GNU utilities or you must ask your system administrator to disable the
124 set-group-id bit on GNU make.
132 # XXX EXPERIMENTAL A.D. 2/27/1998
133 # XXX This script UU/cc.cbu will get 'called-back' by Configure after it
134 # XXX has prompted the user for the C compiler to use.
135 cat > UU/cc.cbu <<'EOSH'
136 # If the C compiler is gcc:
137 # - check the fixed-includes
138 # - check as(1) and ld(1), they should not be GNU
139 # (GNU as and ld 2.8.1 and later are reportedly ok, however.)
140 # If the C compiler is not gcc:
141 # - check as(1) and ld(1), they should not be GNU
142 # (GNU as and ld 2.8.1 and later are reportedly ok, however.)
144 # Watch out in case they have not set $cc.
146 # Perl compiled with some combinations of GNU as and ld may not
147 # be able to perform dynamic loading of extensions. If you have a
148 # problem with dynamic loading, be sure that you are using the Solaris
149 # /usr/ccs/bin/as and /usr/ccs/bin/ld. You can do that with
150 # sh Configure -Dcc='gcc -B/usr/ccs/bin/'
151 # (note the trailing slash is required).
152 # Combinations that are known to work with the following hints:
154 # gcc-2.7.2, GNU as 2.7, GNU ld 2.7
155 # egcs-1.0.3, GNU as 2.9.1 and GNU ld 2.9.1
156 # --Andy Dougherty <doughera@lafayette.edu>
157 # Tue Apr 13 17:19:43 EDT 1999
159 # Get gcc to share its secrets.
160 echo 'main() { return 0; }' > try.c
161 # Indent to avoid propagation to config.sh
162 verbose=`${cc:-cc} -v -o try try.c 2>&1`
164 if echo "$verbose" | grep '^Reading specs from' >/dev/null 2>&1; then
169 tmp=`echo "$verbose" | grep '^Reading' |
170 awk '{print $NF}' | sed 's/specs$/include/'`
172 # Determine if the fixed-includes look like they'll work.
173 # Doesn't work anymore for gcc-2.7.2.
175 # See if as(1) is GNU as(1). GNU as(1) might not work for this job.
176 if echo "$verbose" | grep ' /usr/ccs/bin/as ' >/dev/null 2>&1; then
181 NOTE: You are using GNU as(1). GNU as(1) might not build Perl. If you
182 have trouble, you can use /usr/ccs/bin/as by including -B/usr/ccs/bin/
183 in your ${cc:-cc} command. (Note that the trailing "/" is required.)
186 # Apparently not needed, at least for as 2.7 and later.
187 # cc="${cc:-cc} -B/usr/ccs/bin/"
190 # See if ld(1) is GNU ld(1). GNU ld(1) might not work for this job.
191 # Recompute $verbose since we may have just changed $cc.
192 verbose=`${cc:-cc} -v -o try try.c 2>&1 | grep ld 2>&1`
194 if echo "$verbose" | grep ' /usr/ccs/bin/ld ' >/dev/null 2>&1; then
195 # Ok, gcc directly calls the Solaris /usr/ccs/bin/ld.
197 elif echo "$verbose" | grep "ld: Software Generation Utilities" >/dev/null 2>&1; then
198 # Hmm. gcc doesn't call /usr/ccs/bin/ld directly, but it
199 # does appear to be using it eventually. egcs-1.0.3's ld
201 # All Solaris versions of ld I've seen contain the magic
202 # string used in the grep.
205 # No evidence yet of /usr/ccs/bin/ld. Some versions
206 # of egcs's ld wrapper call /usr/ccs/bin/ld in turn but
207 # apparently don't reveal that unless you pass in -V.
208 # (This may all depend on local configurations too.)
210 myld=`echo $verbose| grep ld | awk '/\/ld/ {print $1}'`
211 # This assumes that gcc's output will not change, and that
212 # /full/path/to/ld will be the first word of the output.
213 # Thus myld is something like opt/gnu/sparc-sun-solaris2.5/bin/ld
215 if $myld -V 2>&1 | grep "ld: Software Generation Utilities" >/dev/null 2>&1; then
216 # Ok, /usr/ccs/bin/ld eventually does get called.
221 NOTE: You are using GNU ld(1). GNU ld(1) might not build Perl. If you
222 have trouble, you can use /usr/ccs/bin/ld by including -B/usr/ccs/bin/
223 in your ${cc:-cc} command. (Note that the trailing "/" is required.)
225 I will try to use GNU ld by passing in the -Wl,-E flag, but if that
226 doesn't work, you should use -B/usr/ccs/bin/ instead.
229 ccdlflags="$ccdlflags -Wl,-E"
230 lddlflags="$lddlflags -W,l-E -G"
239 # See if as(1) is GNU as(1). GNU might not work for this job.
240 case `as --version < /dev/null 2>&1` in
244 NOTE: You are using GNU as(1). GNU as(1) might not build Perl.
245 You must arrange to use /usr/ccs/bin/as, perhaps by adding /usr/ccs/bin
246 to the beginning of your PATH.
252 # See if ld(1) is GNU ld(1). GNU ld(1) might not work for this job.
253 # ld --version doesn't properly report itself as a GNU tool,
254 # as of ld version 2.6, so we need to be more strict. TWP 9/5/96
256 case `ld --version < /dev/null 2>&1` in
257 *GNU*|ld\ version\ 2*)
263 # Try to guess from path
264 case `type ld | awk '{print $NF}'` in
272 NOTE: You are apparently using GNU ld(1). GNU ld(1) might not build Perl.
273 You should arrange to use /usr/ccs/bin/ld, perhaps by adding /usr/ccs/bin
274 to the beginning of your PATH.
281 # as --version or ld --version might dump core.
288 # This script UU/usethreads.cbu will get 'called-back' by Configure
289 # after it has prompted the user for whether to use threads.
290 cat > UU/usethreads.cbu <<'EOCBU'
291 case "$usethreads" in
293 ccflags="-D_REENTRANT $ccflags"
295 # sched_yield is in -lposix4
296 set `echo X "$libswanted "| sed -e 's/ c / posix4 pthread c /'`
300 # On Solaris 2.6 x86 there is a bug with sigsetjmp() and siglongjmp()
301 # when linked with the threads library, such that whatever positive
302 # value you pass to siglongjmp(), sigsetjmp() returns 1.
303 # Thanks to Simon Parsons <S.Parsons@ftel.co.uk> for this report.
304 # Sun BugID is 4117946, "sigsetjmp always returns 1 when called by
305 # siglongjmp in a MT program". As of 19980622, there is no patch
308 /* Test for sig(set|long)jmp bug. */
316 ret = sigsetjmp(env, 1);
317 if (ret) { return ret == 2; }
321 if test "`arch`" = i86pc -a "$osvers" = 2.6 && \
322 ${cc:-cc} try.c -lpthread >/dev/null 2>&1 && ./a.out; then
326 You will see a *** WHOA THERE!!! *** message from Configure for
327 d_sigsetjmp. Keep the recommended value. See hints/solaris_2.sh
328 for more information.
336 case "$uselargefiles" in
337 ''|$define|true|[yY]*)
338 ccflags="$ccflags `getconf LFS_CFLAGS 2>/dev/null`"
339 ldflags="$ldflags `getconf LFS_LDFLAGS 2>/dev/null`"
340 libswanted="$libswanted `getconf LFS_LIBS 2>/dev/null|sed -e 's@^-l@@' -e 's@ -l@ @g`"
344 # This script UU/use64bitint.cbu will get 'called-back' by Configure
345 # after it has prompted the user for whether to use 64 bits.
346 cat > UU/use64bitint.cbu <<'EOCBU'
347 case "$use64bitint" in
352 Solaris `uname -r` does not support 64-bit integers.
353 You should upgrade to at least Solaris 2.7.
358 # When a 64-bit cc becomes available $archname64
359 # may need setting so that $archname gets it attached.
364 case "$use64bitall" in
366 ccflags="$ccflags `getconf XBS5_LP64_OFF64_CFLAGS`"
367 ldflags="$ccflags `getconf XBS5_LP64_OFF64_LDFLAGS`"
368 lddlflags="$lddlflags -G `getconf XBS5_LP64_OFF64_LDFLAGS`"
369 loclibpth="$loclibpth /usr/lib/sparcv9"
370 libscheck='case "`file $xxx`" in
371 *64-bit*|*SPARCV9*) ;;
372 *) xxx=/no/64-bit$xxx ;;
377 # This is just a trick to include some useful notes.
378 cat > /dev/null <<'End_of_Solaris_Notes'
380 Here are some notes kindly contributed by Dean Roehrich.
383 Generic notes about building Perl5 on Solaris:
384 - Use /usr/ccs/bin/make.
385 - If you use GNU make, remove its setgid bit.
386 - Remove all instances of *ucb* from your path.
387 - Make sure libucb is not in /usr/lib (it should be in /usr/ucblib).
388 - Do not use GNU as or GNU ld, or any of GNU binutils or GNU libc.
389 - Do not use /usr/ucb/cc.
390 - Do not change Configure's default answers, except for the path names.
391 - Do not use -lmalloc.
392 - Do not build on SunOS 4 and expect it to work properly on SunOS 5.
393 - /dev/fd must be mounted if you want set-uid scripts to work.
396 Here are the gcc-related questions and answers from the Solaris 2 FAQ. Note
399 - run fixincludes correctly
400 - don't use GNU as or GNU ld
402 Question 5.7 covers the __builtin_va_alist problem people are always seeing.
403 Question 6.1.3 covers the GNU as and GNU ld issues which are always biting
405 Question 6.9 is for those who are still trying to compile Perl4.
407 The latest Solaris 2 FAQ can be found in the following locations:
408 rtfm.mit.edu:/pub/usenet-by-group/comp.sys.sun.admin
409 ftp.fwi.uva.nl:/pub/solaris
411 Perl5 comes with a script in the top-level directory called "myconfig" which
412 will print a summary of the configuration in your config.sh. My summary for
413 Solaris 2.4 and gcc 2.6.3 follows. I have also built with gcc 2.7.0 and the
414 results are identical. This configuration was generated with Configure's -d
415 option (take all defaults, don't bother prompting me). All tests pass for
418 Summary of my perl5 (patchlevel 1) configuration:
420 osname=solaris, osver=2.4, archname=sun4-solaris
421 uname='sunos poplar 5.4 generic_101945-27 sun4d sparc '
424 cc='gcc', optimize='-O', ld='gcc'
428 stdchar='unsigned char', d_stdstdio=define, usevfork=false
429 voidflags=15, castflags=0, d_casti32=define, d_castneg=define
430 intsize=4, alignbytes=8, usemymalloc=y, randbits=15
433 libpth=/lib /usr/lib /usr/ccs/lib /usr/local/lib
434 libs=-lsocket -lnsl -ldl -lm -lc -lcrypt
435 libc=/usr/lib/libc.so
437 dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef
438 cccdlflags='-fpic', ccdlflags=' ', lddlflags='-G'
447 From: Casper.Dik@Holland.Sun.COM (Casper H.S. Dik - Network Security Engineer)
448 Subject: Solaris 2 Frequently Asked Questions (FAQ) 1.48
449 Date: 25 Jul 1995 12:20:18 GMT
451 5.7) Why do I get __builtin_va_alist or __builtin_va_arg_incr undefined?
453 You're using gcc without properly installing the gcc fixed
454 include files. Or you ran fixincludes after installing gcc
455 w/o moving the gcc supplied varargs.h and stdarg.h files
456 out of the way and moving them back again later. This often
457 happens when people install gcc from a binary distribution.
458 If there's a tmp directory in gcc's include directory, fixincludes
459 didn't complete. You should have run "just-fixinc" instead.
461 Another possible cause is using ``gcc -I/usr/include.''
463 6.1) Where is the C compiler or where can I get one?
469 Gcc is available from the GNU archives in source and binary
470 form. Look in a directory called sparc-sun-solaris2 for
471 binaries. You need gcc 2.3.3 or later. You should not use
472 GNU as or GNU ld. Make sure you run just-fixinc if you use
473 a binary distribution. Better is to get a binary version and
474 use that to bootstrap gcc from source.
478 When you install gcc, don't make the mistake of installing
479 GNU binutils or GNU libc, they are not as capable as their
480 counterparts you get with Solaris 2.x.
482 6.9) I can't get perl 4.036 to compile or run.
484 Run Configure, and use the solaris_2_0 hints, *don't* use
485 the solaris_2_1 hints and don't use the config.sh you may
486 already have. First you must make sure Configure and make
487 don't find /usr/ucb/cc. (It must use gcc or the native C
488 compiler: /opt/SUNWspro/bin/cc)
490 Some questions need a special answer.
492 Are your system (especially dbm) libraries compiled with gcc? [y] y
494 yes: gcc 2.3.3 or later uses the standard calling
495 conventions, same as Sun's C.
497 Any additional cc flags? [ -traditional -Dvolatile=__volatile__
498 -I/usr/ucbinclude] -traditional -Dvolatile=__volatile__
499 Remove /usr/ucbinclude.
501 Any additional libraries? [-lsocket -lnsl -ldbm -lmalloc -lm
502 -lucb] -lsocket -lnsl -lm
504 Don't include -ldbm, -lmalloc and -lucb.
506 Perl 5 compiled out of the box.
508 7.0) 64-bitness, from Alan Burlison (added by jhi 2000-02-21)
510 You need a machine running Solaris 2.7 or above.
514 1. Solaris 2.7 and above will run in either 32 bit or 64 bit mode,
516 2. You can build 64 bit apps whilst running 32 bit mode and vice-versa.
517 3. 32 bit apps will run under Solaris running in either 32 or 64 bit mode.
518 4. 64 bit apps require Solaris to be running 64 bit mode
519 5. It is possible to select the appropriate 32 or 64 bit version of an
520 app at run-time using isaexec(3).
521 6. You can detect the OS mode using "isainfo -v", e.g.
522 fubar$ isainfo -v # Ultra 30 in 64 bit mode
523 64-bit sparcv9 applications
524 32-bit sparc applications
525 7. To compile 64 bit you need to use the flag "-xarch=v9".
526 getconf(1) will tell you this, e.g.
527 fubar$ getconf -a | grep v9
528 XBS5_LP64_OFF64_CFLAGS: -xarch=v9
529 XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
530 XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
531 XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
532 XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
533 XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
534 _XBS5_LP64_OFF64_CFLAGS: -xarch=v9
535 _XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
536 _XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
537 _XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
538 _XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
539 _XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
541 > > Now, what should we do, then? Should -Duse64bits in a v9 box cause
542 > > Perl to compiled in v9 mode? Or should we for compatibility stick
543 > > with 32 bit builds and let the people in the know to add the -xarch=v9
544 > > to ccflags (and ldflags?)?
546 > I think the second (explicit) mechanism should be the default. Unless
547 > you want to allocate more than ~ 4Gb of memory inside Perl, you don't
548 > need Perl to be a 64-bit app. Put it this way, on a machine running
549 > Solaris 8, there are 463 executables under /usr/bin, but only 15 of
550 > those require 64 bit versions - mainly because they invade the kernel
551 > address space, e.g. adb, kgmon etc. Certainly we don't recommend users
552 > to build 64 bit apps unless they need the address space.