summaryrefslogtreecommitdiff
path: root/hints
Commit message (Collapse)AuthorAgeFilesLines
* Bump the perl version in various places for 5.15.9Abigail2012-03-192-3/+3
|
* Bump versions from 5.15.7 to 5.15.8Max Maischein2012-02-202-3/+3
|
* Further eliminate POSIX-emulation under LinuxThreadsÆvar Arnfjörð Bjarmason2012-02-151-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Under POSIX threads the getpid() and getppid() functions return the same values across multiple threads, i.e. threads don't have their own PID's. This is not the case under the obsolete LinuxThreads where each thread has a different PID, so getpid() and getppid() will return different values across threads. Ever since the first perl 5.0 we've returned POSIX-consistent semantics for $$, until v5.14.0-251-g0e21945 when the getpid() cache was removed. In 5.8.1 Rafael added further explicit POSIX emulation in perl-5.8.0-133-g4d76a34 [1] by explicitly caching getppid(), so that multiple threads would always return the same value. I don't think all this effort to emulate POSIX sematics is worth it. I think $$ and getppid() are OS-level functions that should always return the same as their C equivalents. I shouldn't have to use a module like Linux::Pid to get the OS version of the return values. This is pretty much a complete non-issue in practice these days, LinuxThreads was a Linux 2.4 thread implementation that nobody maintains anymore[2], all modern Linux distros use NPTL threads which don't suffer from this discrepancy. Debian GNU/kFreeBSD does use LinuxThreads in the 6.0 release, but they too will be moving away from it in future releases, and really, nobody uses Debian GNU/kFreeBSD anyway. This caching makes it unnecessarily tedious to fork an embedded Perl interpreter. When someone that constructs an embedded perl interpreter and forks their application, the fork(2) system call isn't going to run Perl_pp_fork(), and thus the return value of $$ and getppid() doesn't reflect the current process. See [3] for a bug in uWSGI related to this, and Perl::AfterFork on the CPAN for XS code that you need to run after forking a PerlInterpreter unbeknownst to perl. We've already been failing the tests in t/op/getpid.t on these Linux systems that nobody apparently uses, the Debian GNU/kFreeBSD users did notice and filed #96270, this patch fixes that failure by changing the tests to test for different behavior under LinuxThreads, I've tested that this works on my Debian GNU/kFreeBSD 6.0.4 virtual machine. If this change is found to be unacceptable (i.e. we want to continue to emulate POSIX thread semantics for the sake of LinuxThreads) we also need to revert v5.14.0-251-g0e21945, because currently we're only emulating POSIX semantics for getppid(), not getpid(). But I don't think we should do that, both v5.14.0-251-g0e21945 and this commit are awesome. This commit includes a change to embedvar.h made by "make regen_headers". 1. http://www.nntp.perl.org/group/perl.perl5.porters/2002/08/msg64603.html 2. http://pauillac.inria.fr/~xleroy/linuxthreads/ 3. http://projects.unbit.it/uwsgi/ticket/85
* fix cygwin -Uuseithreads hintsReini Urban2012-02-081-1/+1
| | | | | Before -Uuseithreads resulted in a threaded perl. Now -Uuseithreads and -Uusethreads DWIM
* Bump the perl version in various places for v5.15.7Chris 'BinGOs' Williams2012-01-202-3/+3
|
* Bump the perl version in various places for 5.15.6Dave Rolsky2011-12-192-3/+3
|
* Bump the perl version for 5.15.5Steve Hay2011-11-202-3/+3
|
* turn off buggy optimisations in one HP compilerZefram2011-11-171-2/+15
| | | | Fixes [perl #103668].
* Sun cc and CC do not support gcc attributes.Reini Urban2011-11-171-0/+16
| | | | Similar code as in linux.sh
* Detect SunOS CC workshop c++ compilerReini Urban2011-11-171-2/+12
| | | | | Solaris 11 SunStudio 12.2. ships without cc, so CC must be used. Detect it and set ccversion correctly
* enable LFS on GNU/HurdPino Toscano2011-11-061-0/+13
| | | | | | | | | | | | | | | | | | at the moment, perl is compiled on GNU/Hurd without large file support. This, other than the lacking of support for files > 2 GB, causes the failure in the t/op/stat.t test. The failure in stat.t happens because of the following: when filtering devices in /dev/* using grep {} with -b/-c, stat fails for large devices such as /dev/hdX blocks, or /dev/zero chars (this latter case should be an Hurd-specific issue, but shouldn't matter for this case), hence the counts done with grep {} and the ones done filtering the output of `ls' don't match. The attached patch enables the LFS using the same way used on linux.sh; about t/op/lfs.t, it gets skipped at the "kernel/fs not configured to use large files?" check, although it correctly detects sparse files and (at least by looking at the disk usage) allocates the 5GB (or so) file created with system() in that test.
* Build perl using the dynamic linking capabilities of OpenVOS Release 17.1. ↵Paul Green2011-11-041-93/+25
| | | | Remove private copies of some POSIX functions that are now implemented by OpenVOS.
* Improve general GNU hints, needed for GNU/Hurd.Pino Toscano2011-10-311-0/+12
| | | | | | | | Bug-Debian: http://bugs.debian.org/636609 Patch-Name: fixes/hurd-hints.diff With minor modifications to add Pino to AUTHORS.
* Correct FreeBSD hints file for FreeBSD 10.0Jilles Tjoelker2011-10-301-3/+4
| | | | | | | | | | | Perl does not build on FreeBSD 10.0 because some checks in hints/freebsd.sh think FreeBSD 10 is FreeBSD 1 and therefore enable behaviour only appropriate for a.out systems. The below patch was included in the lang/perl5.12 port and fixes its build. The resulting binaries are also suitable to compile other ports. I have also verified that this patch applies to lang/perl5.10 and lang/perl5.14, making them build.
* Bump the perl version in various places for 5.15.4Florian Ragwitz2011-10-201-2/+2
|
* bump version to 5.15.3 using Porting/bump-perl-versionStevan Little2011-09-201-2/+2
|
* The Borland Chainsaw MassacreSteve Hay2011-09-101-2/+1
| | | | | Remove support for the Borland C++ compiler on Win32, as agreed here: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2011-09/msg00034.html
* bump version to 5.12.2 using Porting/bump-perl-versionRicardo Signes2011-08-201-2/+2
|
* Support gcc-4.x on HP-UX PA-RISC/64H.Merijn Brand2011-08-041-0/+10
| | | | | | | | | | | | | | | | | | | Correct the socketsize. Probably due to big-endian versus little-endian, this has always worked on Intel CPUs. This is a very very old problem, and it has been the reason I never used gcc-4 on PA-RISC, because perl would not pass the test suite in 64bitall. Noticeable effects of wrong "$socksizetype" are return codes of 0 (pass) from functions like getpeername (), but invalid (or none) data in the returned structures or a return length of 0 or 256. In the latter case, the length is stored in the second part of the 64bit long and the 32bit first part is 0. This might be true on Intel-like machines too, but the tests will pass, as the significant part of the returned length is in the first 32bits and a pointer to int will still see that correct. Mind that in that case the 32bits after that might have been overridden => can of worms.
* bump perl version number to 5.15.1Zefram2011-07-201-2/+2
|
* Don't include libutil.h on LinuxFlorian Ragwitz2011-07-131-0/+3
| | | | | All it does is cause warnings on recent systems with that header installed. It's required for some variants of FreeBSD only.
* disable use of nm on darwinRicardo Signes2011-07-061-2/+4
| | | | | Testing from 10.5 with Xcode 3 to the latest OS X works with usenm='false' but not always with usenm='true'
* Prefer the system gcc when searching for libraries such as -lmNicholas Clark2011-06-181-1/+9
| | | | | | | 40f026236b9959b7 added code to the Linux hints file to use gcc to locate libraries such as -lm. However, if the user has their own gcc earlier in $PATH than the system gcc, we don't want its libraries. So try to prefer the system gcc.
* Fix some broken URLs found by Porting/checkURL.plLeon Brocard2011-06-122-2/+2
|
* Make hints/gnu.sh append to $ccflags rather than overriding themSamuel Thibault2011-06-051-1/+1
| | | | | | | Bug-Debian: http://bugs.debian.org/587901 Don't override possible extra $ccflags values given to Configure on GNU/Hurd.
* [perl #90306] Fix simple typosMarcel Grünauer2011-05-191-1/+1
|
* Bump the perl version in various places for 5.15.0David Mitchell2011-05-182-10/+10
|
* Typo in commit b641685 breaks Solaris-x64 with Sun ccJan Dubois2011-04-251-1/+1
|
* collapse plibpth to one line and remove trailing /Andy Dougherty2011-04-181-2/+4
| | | | | | | | | | | The recent change to hints/linux.sh, 40f026236b9959b7ad3260fedc6c66cd30bb7abc set the plibpth variable. It was supposed to set all entries on a single line, but it didn't. Do it now, and also remove trailing /'s. (The collapsing is a more robust version of the previous commit, since reverted, that davem wrote independently).
* Revert "collapse plibpth to one line"David Mitchell2011-04-181-2/+1
| | | | | | This reverts commit 55e4a474ad63535e486bd657f45b5339709cbcd3. In improved version is coming next...
* collapse plibpth to one lineDavid Mitchell2011-04-181-1/+2
| | | | | | | | The recent change to hints/linux.sh, 40f026236b9959b7ad3260fedc6c66cd30bb7abc set the plibpth variable. It was supposed to set all entries on a single line, but it didn't. Do it now,
* check --whole-archive is supported (in cc.cbu) before using itTony Cook2011-04-181-1/+11
| | | | | netbsd for pre 4.6 gcc requires --whole-archive to build shared libraries, but this is rejected and not required in 4.6.0.
* Revert "check --whole-archive is supported before using it"Tony Cook2011-04-181-9/+1
| | | | | | This reverts commit 673d8593b7ef274dadbfff97fd641e3c563fc716. I meant to apply the cc.cbu version of this patch.
* As part of their switch to a multi-arch library layout,Andy Dougherty2011-04-171-0/+18
| | | | | | | | | | | | | | | Ubuntu 11.04 (and later, presumably) doesn't keep most libraries (such as -lm) in /lib or /usr/lib. So we have to ask gcc to tell us where to look. We don't want gcc's own libraries, however, so we filter those out. This could be conditional on Ubuntu, but other distributions have announced their intent follow suit, and this scheme seems to work even on rather old gcc's. This unconditionally uses gcc because even if the user is using another compiler, we still need to find the math library and friends, and I don't know how other compilers will cope with that situation. Still, as an escape hatch, allow Configure command line overrides to plibpth to bypass this check.
* check --whole-archive is supported before using itTony Cook2011-04-131-1/+9
| | | | | | | | netbsd for pre 4.6 gcc requires --whole-archive to build shared libraries, but this is rejected and not required in 4.6.0. Simply changing the option to -Wl,--whole-archive works on gcc 4.6.0 but fails for the system cc on NetBSD 5.1/x64.
* In Darwin's hints, only add -no-cpp-precomp to ccflags if it's not an error.Nicholas Clark2011-04-051-4/+6
| | | | | | | | | | | Previously -no-cpp-precomp was added uncondtionally to cppflags and ccflags. Apple's compiler accepts this unconditionally. gcc 4.5 warns about it, but ignores it. gcc 4.6 treats the unknown flag as an error. Hence test whether the flag causes problems, and only add it if it does not. (Searching with Google suggests that this flag has been unnecessary on OS X for some time. However, there's no clear documentation about it to confirm when it stopped being necessary.)
* First provisional bump to 5.14.0-RC0Jesse Vincent2011-04-022-10/+10
|
* Bump the perl version for 5.13.11Florian Ragwitz2011-03-201-2/+2
|
* [perl #85738] cc deprecated option warnings on solaris 10 sparc 64-bitArvan2011-03-091-3/+15
| | | | | | | | | | | | | | When building on Solaris 10 multiple warnings are produced saying: Warning: -xarch=generic64 is deprecated, use -m64 to create 64-bit programs This is because the config script hints/solaris_2.sh uses the values returned by getconf which are incorrect for newer versions of Sun's compiler. I believe they are correct for earlier versions, but do not have a system to test this on. This change to solaris_2.sh checks that the compiler produces this warning, and if so updates the flags to the correct values.
* Bump the perl version in various places to 5.13.10Ævar Arnfjörð Bjarmason2011-02-201-2/+2
| | | | | | | | | | Done with: ./perl -Ilib Porting/bump-perl-version -s 5.13.9 5.13.10 > /tmp/scan ./perl -Ilib Porting/bump-perl-version -u < /tmp/scan And then manually editing the README.vms file to update the vmstar example.
* Tracked down some other places to make the Unicode-Collate changesChris 'BinGOs' Williams2011-01-231-2/+2
|
* Bump the perl version in various places to 5.13.9Jesse Vincent2011-01-201-2/+2
|
* Revert "Tracked down some other places to make the Unicode-Collate changes"Chris 'BinGOs' Williams2011-01-191-2/+2
| | | | | | This reverts commit 7dc5472a0a41a8396671d5586d4c1254a1cb5e8c. Back out XS switch over
* Tracked down some other places to make the Unicode-Collate changesChris 'BinGOs' Williams2011-01-171-2/+2
|
* Fix typos (spelling errors) in hints/*.Peter J. Acklam) (via RT2011-01-0716-20/+20
| | | | | | | | | # New Ticket Created by (Peter J. Acklam) # Please include the string: [perl #81884] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81884 > Signed-off-by: Abigail <abigail@abigail.be>
* Actuall excise 'Apollo DomainOS' support. We officially killed it in 5.11.0. ItJesse Vincent2011-01-041-55/+0
| | | | hadn't worked for years before that.
* Update cygwin hintsReini Urban2011-01-041-5/+1
| | | | | | do not use usemymalloc (double size + slow) remove deprecated libcygipc info remove overlarge stack size
* bump perl version number for 5.13.8Zefram2010-12-191-2/+2
|
* Remove "dead" RCS $Id$ tags from files that we own.Nicholas Clark2010-12-162-3/+0
| | | | | All files have been modified more recently than their tag, rendering information in the tag redundant.
* Change the default for usemymalloc to 'n' for NetBSDChris 'BinGOs' Williams2010-11-291-0/+9
| | | | | | It should not be the default, it isn't the default when perl is built in pkgsrc and from personal experience using perl's malloc as the default is to enter a world of pain and suffering.