perl 5.003_01: lib/File/Basename.pm
[p5sagit/p5-mst-13.2.git] / hints / next_3_2.sh
CommitLineData
04e3c97b 1# This file has been put together by Anno Siegel <siegel@zrz.TU-Berlin.DE>
2# and Andreas Koenig <k@franz.ww.TU-Berlin.DE>. Comments, questions, and
3# improvements welcome!
4#
5# These hints are intended for NeXT 3.2.
6
7# From about perl5.002beta1h perl became unstable on the
8# NeXT. Intermittent coredumps were frequent on 3.2 OS. There were
9# reports, that the developer version of 3.3 didn't have problems, so it
10# seemed pretty obvious that we had to work around an malloc bug in 3.2.
11# This hints file reflects a patch to perl5.002_01 that introduces a
12# home made sbrk routine (remember, NeXT's sbrk _never_ worked). This
13# sbrk makes it possible to run perl with its own malloc. Thanks to
14# Ilya who showed me the way to his sbrk for OS/2!!
15# andreas koenig, 1996-06-16
16
17ccflags='-DUSE_NEXT_CTYPE -DUSE_PERL_SBRK -DHIDEMYMALLOC'
18POSIX_cflags='ccflags="-posix $ccflags"'
19ldflags='-u libsys_s'
20libswanted='dbm gdbm db'
21
22lddlflags='-r'
23# Give cccdlflags an empty value since Configure will detect we are
24# using GNU cc and try to specify -fpic for cccdlflags.
25cccdlflags=' '
26
27i_utime='undef'
28groupstype='int'
29direntrytype='struct direct'
30d_strcoll='undef'
31
32# the simple program `for ($i=1;$i<38771;$i++){$t{$i}=123}' fails
33# with Larry's malloc on NS 3.2 due to broken sbrk()
34######################################################################
35# above comment should stay here, but is not longer of importance #
36# with -DUSE_PERL_SBRK and -DHIDEMYMALLOC we can now say 'yes' to #
37# usemymalloc. We call this hintsfile next_3_2.sh, so folks with 3.3 #
38# can decide what they prefer. Actually folks with 3.3 "user" version#
39# will also need this hintsfile, but how can I discern which 3.3 it #
40# is? #
41######################################################################
42usemymalloc='y'
43
44d_uname='define'
45d_setpgid='define'
46d_setsid='define'
47d_tcgetpgrp='define'
48d_tcsetpgrp='define'
49
50#
51# On some NeXT machines, the timestamp put by ranlib is not correct, and
52# this may cause useless recompiles. Fix that by adding a sleep before
53# running ranlib. The '5' is an empirical number that's "long enough."
54#
55ranlib='sleep 5; /bin/ranlib'
56
57
58#
59# There where reports that the compiler on HPPA machines
60# fails with the -O flag on pp.c.
61#
62if [ `arch` = "hppa" ]; then
63pp_cflags='optimize="-g"'
64fi