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'
10 POSIX_cflags='ccflags="-posix $ccflags"'
12 libswanted='dbm gdbm db'
14 lddlflags='-nostdlib -r'
15 # Give cccdlflags an empty value since Configure will detect we are
16 # using GNU cc and try to specify -fpic for cccdlflags.
20 # Change the line below if you do not want to build 'quad-fat'
23 archs=`/bin/lipo -info /usr/lib/libm.a | sed 's/^[^:]*:[^:]*: //'`
35 direntrytype='struct direct'
38 ######################################################################
40 ######################################################################
42 # the simple program `for ($i=1;$i<38771;$i++){$t{$i}=123}' fails
43 # with Larry's malloc on NS 3.2 due to broken sbrk()
45 # setting usemymalloc='n' was the solution back then. Later came
46 # reports that perl would run unstable on 3.2:
48 # From about perl5.002beta1h perl became unstable on the
49 # NeXT. Intermittent coredumps were frequent on 3.2 OS. There were
50 # reports, that the developer version of 3.3 didn't have problems, so it
51 # seemed pretty obvious that we had to work around an malloc bug in 3.2.
52 # This hints file reflects a patch to perl5.002_01 that introduces a
53 # home made sbrk routine (remember, NeXT's sbrk _never_ worked). This
54 # sbrk makes it possible to run perl with its own malloc. Thanks to
55 # Ilya who showed me the way to his sbrk for OS/2!!
56 # andreas koenig, 1996-06-16
58 # So, this hintsfile is using perl's malloc. If you want to turn perl's
59 # malloc off, you need to change remove '-DUSE_PERL_SBRK' and
60 # '-DHIDEMYMALLOC' from the ccflags above and set usemymalloc below
63 ######################################################################
73 # On some NeXT machines, the timestamp put by ranlib is not correct, and
74 # this may cause useless recompiles. Fix that by adding a sleep before
75 # running ranlib. The '5' is an empirical number that's "long enough."
77 ranlib='sleep 5; /bin/ranlib'
80 # There where reports that the compiler on HPPA machines
81 # fails with the -O flag on pp.c.
82 pp_cflags='optimize="-g"'