diff options
author | Lupe Christoph <lupe@lupe-christoph.de> | 2001-01-29 13:59:36 +0100 |
---|---|---|
committer | Jarkko Hietaniemi <jhi@iki.fi> | 2001-01-29 15:29:11 +0000 |
commit | 83bd2f301548cca99336e63125a11e63aad34313 (patch) | |
tree | b3217d4cc92cf9ea7bf66d297faa5345b8b3803d | |
parent | 20fb949fed790d46b0900443523ae4205f81da71 (diff) | |
download | perl-83bd2f301548cca99336e63125a11e63aad34313.tar.gz |
MAking Solaris malloc() the default
Message-ID: <20010129125936.Z4830@alanya.lupe-christoph.de>
The README.solaris part slightly tweaked.
p4raw-id: //depot/perl@8588
-rw-r--r-- | README.solaris | 27 | ||||
-rw-r--r-- | hints/solaris_2.sh | 13 |
2 files changed, 20 insertions, 20 deletions
diff --git a/README.solaris b/README.solaris index 97e84a3622..1a36a8a94a 100644 --- a/README.solaris +++ b/README.solaris @@ -358,13 +358,6 @@ instead. All this should be handled automatically by the hints file, if requested. -If you do want to be able to allocate more than 4GB memory inside -perl, then you should use the Solaris malloc, since the perl -malloc breaks when dealing with more than 2GB of memory. You can do -this with - - sh Configure -Uusemymalloc - =head3 Long Doubles. As of 5.6.0, long doubles are not working. @@ -379,22 +372,22 @@ in -lrt. The hints file should handle adding this automatically. =head2 Malloc Issues. +Starting from Perl 5.7.1 Perl uses the Solaris malloc, since the perl +malloc breaks when dealing with more than 2GB of memory, and the Solaris +malloc also seems to be faster. + +If you for some reason (such as binary backward compatibility) really +need to use perl's malloc, you can rebuild Perl from the sources +and Configure the build with + + sh Configure -Dusemymalloc + You should not use perl's malloc if you are building with gcc. There are reports of core dumps, especially in the PDL module. The problem appears to go away under -DDEBUGGING, so it has been difficult to track down. Sun's compiler appears to be ok with or without perl's malloc. [XXX further investigation is needed here.] -You should also not use perl's malloc if you are building perl as -an LP64 application, since perl's malloc has trouble allocating more -than 2GB of memory. - -You can avoid perl's malloc by Configuring with - - sh Configure -Uusemymalloc - -[XXX Update hints file.] - =head1 MAKE PROBLEMS. =over 4 diff --git a/hints/solaris_2.sh b/hints/solaris_2.sh index 0bf5bab3af..86a375bdc5 100644 --- a/hints/solaris_2.sh +++ b/hints/solaris_2.sh @@ -1,5 +1,5 @@ # hints/solaris_2.sh -# Last modified: Tue Jan 2 10:16:35 2001 +# Last modified: Mon Jan 29 12:52:28 2001 # Lupe Christoph <lupe@lupe-christoph.de> # Based on version by: # Andy Dougherty <doughera@lafayette.edu> @@ -26,9 +26,16 @@ # these ought to be harmless. See below for more details. # See man vfork. -usevfork=false +usevfork=${usevfork:-false} -d_suidsafe=define +# Solaris has secure SUID scripts +d_suidsafe=${d_suidsafe:-define} + +# Several people reported problems with perl's malloc, especially +# when use64bitall is defined or when using gcc. +# http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-01/msg01318.html +# http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-01/msg00465.html +usemymalloc=${usemymalloc:-false} # Avoid all libraries in /usr/ucblib. # /lib is just a symlink to /usr/lib |