2 # Last modified: 27 September 1995 by
3 # Andy Dougherty <doughera@lafcol.lafayette.edu>
4 # Based on input from lots of folks, especially
5 # Dean Roehrich <roehrich@ironwood-fddi.cray.com>
11 # Avoid all libraries in /usr/ucblib.
12 set `echo $glibpth | sed -e 's@/usr/ucblib@@'`
14 # Remove bad libraries. -lucb contains incompatible routines.
15 # -lld doesn't do anything useful.
16 # -lmalloc can cause a problem with GNU CC & Solaris. Specifically,
17 # libmalloc.a may allocate memory that is only 4 byte aligned, but
18 # GNU CC on the Sparc assumes that doubles are 8 byte aligned.
19 # Thanks to Hallvard B. Furuseth <h.b.furuseth@usit.uio.no>
20 set `echo " $libswanted " | sed -e 's@ ld @ @' -e 's@ malloc @ @' -e 's@ ucb @ @'`
23 # Look for architecture name. We want to suggest a useful default
24 # for archlib and also warn about possible -x486 flags needed.
27 if test -f /usr/bin/arch; then
28 archname=`/usr/bin/arch`
29 archname="${archname}-${osname}"
30 elif test -f /usr/ucb/arch; then
31 archname=`/usr/ucb/arch`
32 archname="${archname}-${osname}"
37 *86*) echo "For an Intel platform you might need to add -x486 to ccflags" >&4;;
41 # See below for excerpts from the Solaris FAQ.
43 # From roehrich@ironwood-fddi.cray.com Wed Sep 27 12:51:46 1995
44 # Date: Thu, 7 Sep 1995 16:31:40 -0500
45 # From: Dean Roehrich <roehrich@ironwood-fddi.cray.com>
46 # To: perl5-porters@africa.nicoh.com
47 # Subject: Re: On perl5/solaris/gcc
49 # Here's another draft of the perl5/solaris/gcc sanity-checker.
52 */usr/ucb*:/usr/bin:*|*/usr/ucb*:/usr/bin) cat <<END
54 NOTE: Some people have reported problems with /usr/ucb/cc.
55 Remove /usr/ucb from your PATH if you have difficulties.
62 # Check that /dev/fd is mounted. If it is not mounted, let the
63 # user know that suid scripts may not work.
64 /usr/bin/df /dev/fd 2>&1 > /dev/null
70 NOTE: Your system does not have /dev/fd mounted. If you want to
71 be able to use set-uid scripts you must ask your system administrator
79 # See if libucb can be found in /usr/lib. If it is, warn the user
80 # that this may cause problems while building Perl extensions.
81 /usr/bin/ls /usr/lib/libucb* >/dev/null 2>&1
86 NOTE: libucb has been found in /usr/lib. libucb should reside in
87 /usr/ucblib. You may have trouble while building Perl extensions.
94 # See if make(1) is GNU make(1).
95 # If it is, make sure the setgid bit is not set.
96 make -v > make.vers 2>&1
97 if grep GNU make.vers > /dev/null 2>&1; then
98 tmp=`/usr/bin/which make`
99 case "`/usr/bin/ls -l $tmp`" in
103 NOTE: Your PATH points to GNU make, and your GNU make has the set-group-id
104 bit set. You must either rearrange your PATH to put /usr/ccs/bin before the
105 GNU utilities or you must ask your system administrator to disable the
106 set-group-id bit on GNU make.
114 # If the C compiler is gcc:
115 # - check the fixed-includes
116 # - check as(1) and ld(1), they should not be GNU
117 # If the C compiler is not gcc:
118 # - check as(1) and ld(1), they should not be GNU
120 # Watch out in case they have not set $cc.
121 case "`${cc:-cc} -v 2>&1`" in
128 # Get gcc to share its secrets.
129 echo 'main() { return 0; }' > try.c
130 verbose=`${cc:-cc} -v -o try try.c 2>&1`
132 tmp=`echo "$verbose" | grep '^Reading' |
133 awk '{print $NF}' | sed 's/specs$/include/'`
135 # Determine if the fixed-includes look like they'll work.
136 sed 1q $tmp/stdarg.h 2>&1 | grep 'stdarg.h for GNU' 2>&1 >/dev/null
142 NOTE: The fixincludes or just-fixinc script for gcc was not run
143 properly. Your gcc may not be able to compile Perl. Inform your system
144 administrator that ${cc:-cc} is not properly installed.
150 # See if as(1) is GNU as(1). GNU as(1) won't work for this job.
152 */usr/ccs/bin/as*) ;;
156 NOTE: You are using GNU as(1). GNU as(1) will not build Perl.
157 You must arrange to use /usr/ccs/bin/as, perhaps by setting
164 # See if ld(1) is GNU ld(1). GNU ld(1) won't work for this job.
166 */usr/ccs/bin/ld*) ;;
170 NOTE: You are using GNU ld(1). GNU ld(1) will not build Perl.
171 You must arrange to use /usr/ccs/bin/ld, perhaps by setting
185 # See if as(1) is GNU as(1). GNU as(1) won't work for this job.
186 case `as --version < /dev/null 2>&1` in
190 NOTE: You are using GNU as(1). GNU as(1) will not build Perl.
191 You must arrange to use /usr/ccs/bin, perhaps by adding it to the
192 beginning of your PATH.
198 # See if ld(1) is GNU ld(1). GNU ld(1) won't work for this job.
199 case `ld --version < /dev/null 2>&1` in
203 NOTE: You are using GNU ld(1). GNU ld(1) will not build Perl.
204 You must arrange to use /usr/ccs/bin, perhaps by adding it to the
205 beginning of your PATH
214 # as --version or ld --version might dump core.
217 # This is just a trick to include some useful notes.
218 cat > /dev/null <<'End_of_Solaris_Notes'
220 Here are some notes kindly contributed by Dean Roehrich.
223 Generic notes about building Perl5 on Solaris:
224 - Use /usr/ccs/bin/make.
225 - If you use GNU make, remove its setgid bit.
226 - Remove all instances of *ucb* from your path.
227 - Make sure libucb is not in /usr/lib (it should be in /usr/ucblib).
228 - Do not use GNU as or GNU ld, or any of GNU binutils or GNU libc.
229 - Do not use /usr/ucb/cc.
230 - Do not change Configure's default answers, except for the path names.
231 - Do not use -lmalloc.
232 - Do not build on SunOS 4 and expect it to work properly on SunOS 5.
233 - /dev/fd must be mounted if you want set-uid scripts to work.
236 Here are the gcc-related questions and answers from the Solaris 2 FAQ. Note
239 - run fixincludes correctly
240 - don't use GNU as or GNU ld
242 Question 5.7 covers the __builtin_va_alist problem people are always seeing.
243 Question 6.1.3 covers the GNU as and GNU ld issues which are always biting
245 Question 6.9 is for those who are still trying to compile Perl4.
247 The latest Solaris 2 FAQ can be found in the following locations:
248 rtfm.mit.edu:/pub/usenet-by-group/comp.sys.sun.admin
249 ftp.fwi.uva.nl:/pub/solaris
251 Perl5 comes with a script in the top-level directory called "myconfig" which
252 will print a summary of the configuration in your config.sh. My summary for
253 Solaris 2.4 and gcc 2.6.3 follows. I have also built with gcc 2.7.0 and the
254 results are identical. This configuration was generated with Configure's -d
255 option (take all defaults, don't bother prompting me). All tests pass for
258 Summary of my perl5 (patchlevel 1) configuration:
260 osname=solaris, osver=2.4, archname=sun4-solaris
261 uname='sunos poplar 5.4 generic_101945-27 sun4d sparc '
264 cc='gcc', optimize='-O', ld='gcc'
268 stdchar='unsigned char', d_stdstdio=define, usevfork=false
269 voidflags=15, castflags=0, d_casti32=define, d_castneg=define
270 intsize=4, alignbytes=8, usemymalloc=y, randbits=15
273 libpth=/lib /usr/lib /usr/ccs/lib /usr/local/lib
274 libs=-lsocket -lnsl -ldl -lm -lc -lcrypt
275 libc=/usr/lib/libc.so
277 dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef
278 cccdlflags='-fpic', ccdlflags=' ', lddlflags='-G'
287 From: Casper.Dik@Holland.Sun.COM (Casper H.S. Dik - Network Security Engineer)
288 Subject: Solaris 2 Frequently Asked Questions (FAQ) 1.48
289 Date: 25 Jul 1995 12:20:18 GMT
291 5.7) Why do I get __builtin_va_alist or __builtin_va_arg_incr undefined?
293 You're using gcc without properly installing the gcc fixed
294 include files. Or you ran fixincludes after installing gcc
295 w/o moving the gcc supplied varargs.h and stdarg.h files
296 out of the way and moving them back again later. This often
297 happens when people install gcc from a binary distribution.
298 If there's a tmp directory in gcc's include directory, fixincludes
299 didn't complete. You should have run "just-fixinc" instead.
301 Another possible cause is using ``gcc -I/usr/include.''
303 6.1) Where is the C compiler or where can I get one?
309 Gcc is available from the GNU archives in source and binary
310 form. Look in a directory called sparc-sun-solaris2 for
311 binaries. You need gcc 2.3.3 or later. You should not use
312 GNU as or GNU ld. Make sure you run just-fixinc if you use
313 a binary distribution. Better is to get a binary version and
314 use that to bootstrap gcc from source.
318 When you install gcc, don't make the mistake of installing
319 GNU binutils or GNU libc, they are not as capable as their
320 counterparts you get with Solaris 2.x.
322 6.9) I can't get perl 4.036 to compile or run.
324 Run Configure, and use the solaris_2_0 hints, *don't* use
325 the solaris_2_1 hints and don't use the config.sh you may
326 already have. First you must make sure Configure and make
327 don't find /usr/ucb/cc. (It must use gcc or the native C
328 compiler: /opt/SUNWspro/bin/cc)
330 Some questions need a special answer.
332 Are your system (especially dbm) libraries compiled with gcc? [y] y
334 yes: gcc 2.3.3 or later uses the standard calling
335 conventions, same as Sun's C.
337 Any additional cc flags? [ -traditional -Dvolatile=__volatile__
338 -I/usr/ucbinclude] -traditional -Dvolatile=__volatile__
339 Remove /usr/ucbinclude.
341 Any additional libraries? [-lsocket -lnsl -ldbm -lmalloc -lm
342 -lucb] -lsocket -lnsl -lm
344 Don't include -ldbm, -lmalloc and -lucb.
346 Perl 5 compiled out of the box.