perl 5.003_02: [no incremental changelog available]
[p5sagit/p5-mst-13.2.git] / hints / next_4.sh
CommitLineData
760ac839 1######################################################################
25b26da3 2#
3# IMPORTANT: before you run 'make', you need to enter one of these two
4# lines (depending on your shell):
5# DYLD_LIBRARY_PATH=`pwd`; export DYLD_LIBRARY_PATH
6# or
7# setenv DYLD_LIBRARY_PATH `pwd`
8#
760ac839 9######################################################################
10
11# Posix support has been removed from NextStep
12#
25b26da3 13useposix='undef'
14
15altmake='gnumake'
16libpth='/lib /usr/lib'
17libswanted=' '
18libc='/NextLibrary/Frameworks/System.framework/System'
19
20isnext_4='define'
760ac839 21
22#
23# Change the line below if you do not want to build 'quad-fat'
24# binaries
25#
25b26da3 26mab='-arch m68k -arch i386 -arch sparc'
27ldflags='-dynamic -prebind'
28lddlflags='-dynamic -bundle -undefined suppress'
760ac839 29ccflags='-dynamic -fno-common -DUSE_NEXT_CTYPE -DUSE_PERL_SBRK -DHIDEMYMALLOC'
25b26da3 30cccdlflags='none'
31ld='cc'
760ac839 32#optimize='-g -O'
25b26da3 33
34d_shrplib='define'
35dlext='bundle'
36so='dylib'
37
760ac839 38#
39# The default prefix would be '/usr/local'. But since many people are
40# likely to have still 3.3 machines on their network, we do not want
41# to overwrite possibly existing 3.3 binaries.
42#
25b26da3 43prefix='/usr/local/OPENSTEP'
44#archlib='/usr/lib/perl5'
45#archlibexp='/usr/lib/perl5'
46archname='OPENSTEP-Mach'
47
48d_strcoll='undef'
49i_dbm='define'
50i_utime='undef'
51groupstype='int'
52direntrytype='struct direct'
53
760ac839 54######################################################################
55# THE MALLOC STORY
56######################################################################
57# 1994:
25b26da3 58# the simple program `for ($i=1;$i<38771;$i++){$t{$i}=123}' fails
59# with Larry's malloc on NS 3.2 due to broken sbrk()
760ac839 60#
61# setting usemymalloc='n' was the solution back then. Later came
62# reports that perl would run unstable on 3.2:
63#
64# From about perl5.002beta1h perl became unstable on the
65# NeXT. Intermittent coredumps were frequent on 3.2 OS. There were
66# reports, that the developer version of 3.3 didn't have problems, so it
67# seemed pretty obvious that we had to work around an malloc bug in 3.2.
68# This hints file reflects a patch to perl5.002_01 that introduces a
69# home made sbrk routine (remember, NeXT's sbrk _never_ worked). This
70# sbrk makes it possible to run perl with its own malloc. Thanks to
71# Ilya who showed me the way to his sbrk for OS/2!!
72# andreas koenig, 1996-06-16
73#
74# So, this hintsfile is using perl's malloc. If you want to turn perl's
75# malloc off, you need to change remove '-DUSE_PERL_SBRK' and
76# '-DHIDEMYMALLOC' from the ccflags above and set usemymalloc below
77# to 'n'.
78#
79######################################################################
80usemymalloc='y'
25b26da3 81clocktype='int'
82
83#
84# On some NeXT machines, the timestamp put by ranlib is not correct, and
85# this may cause useless recompiles. Fix that by adding a sleep before
86# running ranlib. The '5' is an empirical number that's "long enough."
87# (Thanks to Andreas Koenig <k@franz.ww.tu-berlin.de>)
88ranlib='sleep 5; /bin/ranlib'
89#
90# There where reports that the compiler on HPPA machines
91# fails with the -O flag on pp.c.
92# But since there is no HPPA for OPENSTEP...
93# pp_cflags='optimize="-g"'