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 ######################################################################
11 ######################################################################
13 # the simple program `for ($i=1;$i<38771;$i++){$t{$i}=123}' fails
14 # with Larry's malloc on NS 3.2 due to broken sbrk()
16 # setting usemymalloc='n' was the solution back then. Later came
17 # reports that perl would run unstable on 3.2:
20 # From about perl5.002beta1h perl became unstable on the
21 # NeXT. Intermittent coredumps were frequent on 3.2 OS. There were
22 # reports, that the developer version of 3.3 didn't have problems, so it
23 # seemed pretty obvious that we had to work around an malloc bug in 3.2.
24 # This hints file reflects a patch to perl5.002_01 that introduces a
25 # home made sbrk routine (remember, NeXT's sbrk _never_ worked). This
26 # sbrk makes it possible to run perl with its own malloc. Thanks to
27 # Ilya who showed me the way to his sbrk for OS/2!!
29 # The whole malloc desaster lead to a failing gdbm test. It is far
30 # beyond my understanding, why GDBM_File breaks with the "fix", but in
31 # general I consider it better to have a working perl with broken GDBM
32 # than no perl at all.
34 # So, this hintsfile is using perl's malloc. If you want to turn
35 # perl's malloc off, you need to remove '-DUSE_PERL_SBRK' and
36 # '-DHIDEMYMALLOC' from the ccflags and set usemymalloc to 'n'.
39 # From perl5.003_22 the malloc bug has no impact any more. We can run
40 # a perl without a special sbrk. Apparently Chip Salzenberg, the hero
41 # of 5.004 anyway, earned another trophy during Australien Open.
43 # use the following two lines to enable USE_PERL_SBRK. Try this if you
44 # encounter intermittent core dumps:
45 #ccflags='-DUSE_NEXT_CTYPE -DUSE_PERL_SBRK -DHIDEMYMALLOC'
47 # use the following two lines if you have perl5.003_22 or better and
48 # do not encounter intermittent core dumps.
50 ccflags='-DUSE_NEXT_CTYPE'
53 ######################################################################
54 # End of the MALLOC story
55 ######################################################################
58 libswanted='dbm gdbm db'
60 lddlflags='-nostdlib -r'
61 # Give cccdlflags an empty value since Configure will detect we are
62 # using GNU cc and try to specify -fpic for cccdlflags.
65 ######################################################################
67 ######################################################################
68 # By default we will build for all architectures your development
69 # environment supports. If you only want to build for the platform
70 # you are on, simply comment or remove the line below.
72 # If you want to build for specific architectures, change the line
73 # below to something like
77 archs=`/bin/lipo -info /usr/lib/libm.a | sed -n 's/^[^:]*:[^:]*: //p'`
80 # leave the following part alone
82 archcount=`echo $archs |wc -w`
83 if [ $archcount -gt 1 ]
87 mabflags="$mabflags -arch $d"
89 ccflags="$ccflags $mabflags"
90 ldflags="$ldflags $mabflags"
91 lddlflags="$lddlflags $mabflags"
94 ######################################################################
96 ######################################################################
101 direntrytype='struct direct'
105 # At least on m68k there are situations when memcmp doesn't behave
106 # as expected. So we'll use perl's memcmp.
109 # setpgid() is in the posix library, but we don't use -posix, so
110 # we don't see it. ext/POSIX/POSIX.xs *does* use -posix, so
111 # setpgid is still available as POSIX::setpgid.
112 # See ext/POSIX/POSIX/hints/next.pl.
119 # On some NeXT machines, the timestamp put by ranlib is not correct, and
120 # this may cause useless recompiles. Fix that by adding a sleep before
121 # running ranlib. The '5' is an empirical number that's "long enough."
123 ranlib='sleep 5; /bin/ranlib'
126 # There where reports that the compiler on HPPA machines
127 # fails with the -O flag on pp.c.
128 # Compiling pp.c with -O for HPPA machines results in a broken perl.
129 # This is true whether we're on an HPPA machine or cross-compiling
131 pp_cflags='optimize=""'