1 # This file has been put together by Anno Siegel <siegel@zrz.TU-Berlin.DE>,
2 # Andreas Koenig <k@franz.ww.TU-Berlin.DE> and Gerd Knops <gerti@BITart.com>.
3 # Comments, questions, and improvements welcome!
5 # These hints work for NeXT 3.2 and 3.3. 3.0 has it's own
9 ccflags='-DUSE_NEXT_CTYPE -DUSE_PERL_SBRK -DHIDEMYMALLOC'
11 libswanted='dbm gdbm db'
13 lddlflags='-nostdlib -r'
14 # Give cccdlflags an empty value since Configure will detect we are
15 # using GNU cc and try to specify -fpic for cccdlflags.
19 # Change the line below if you do not want to build 'quad-fat'
22 archs=`/bin/lipo -info /usr/lib/libm.a | sed 's/^[^:]*:[^:]*: //'`
34 direntrytype='struct direct'
37 ######################################################################
39 ######################################################################
41 # the simple program `for ($i=1;$i<38771;$i++){$t{$i}=123}' fails
42 # with Larry's malloc on NS 3.2 due to broken sbrk()
44 # setting usemymalloc='n' was the solution back then. Later came
45 # reports that perl would run unstable on 3.2:
47 # From about perl5.002beta1h perl became unstable on the
48 # NeXT. Intermittent coredumps were frequent on 3.2 OS. There were
49 # reports, that the developer version of 3.3 didn't have problems, so it
50 # seemed pretty obvious that we had to work around an malloc bug in 3.2.
51 # This hints file reflects a patch to perl5.002_01 that introduces a
52 # home made sbrk routine (remember, NeXT's sbrk _never_ worked). This
53 # sbrk makes it possible to run perl with its own malloc. Thanks to
54 # Ilya who showed me the way to his sbrk for OS/2!!
55 # andreas koenig, 1996-06-16
57 # So, this hintsfile is using perl's malloc. If you want to turn perl's
58 # malloc off, you need to change remove '-DUSE_PERL_SBRK' and
59 # '-DHIDEMYMALLOC' from the ccflags above and set usemymalloc below
62 ######################################################################
66 # setpgid() is in the posix library, but we don't use -posix, so
67 # we don't see it. ext/POSIX/POSIX.xs *does* use -posix, so
68 # setpgid is still available as POSIX::setpgid.
69 # See ext/POSIX/POSIX/hints/next.pl.
76 # On some NeXT machines, the timestamp put by ranlib is not correct, and
77 # this may cause useless recompiles. Fix that by adding a sleep before
78 # running ranlib. The '5' is an empirical number that's "long enough."
80 ranlib='sleep 5; /bin/ranlib'
83 # There where reports that the compiler on HPPA machines
84 # fails with the -O flag on pp.c.
85 # Compiling pp.c with -O for HPPA machines results in a broken perl.
86 # This is true whether we're on an HPPA machine or cross-compiling
88 pp_cflags='optimize=""'