| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
After backporting Nicholas' work and slimming down metaconfig.h
|
|
|
|
|
|
|
|
|
| |
In Configure, check whether _NSGetExecutablePath() can be used to find the
absolute pathname of the executable. If so, set usensgetexecutablepath in
config.sh and USE_NSGETEXECUTABLEPATH in config.h. If this is set, then use
this approach in S_set_caret_X() to canonicalise $^X as an absolute
path. This approach works on OS X, and possible on other platforms that
use dyld.
|
|
|
|
|
|
|
|
|
|
| |
In Configure, check whether sysctl() and KERN_PROC_PATHNAME can be used
to find the absolute pathname of the executable. If so, set
usekernprocpathname in config.sh and USE_KERN_PROC_PATHNAME in config.h.
If this is set, then use this approach in S_set_caret_X() to canonicalise
$^X as an absolute path. This approach works on (at least) FreeBSD, and
doesn't rely on the /proc filesystem existing, or /proc/curproc/file being
present.
|
| |
|
|
|
|
|
|
|
|
|
| |
This means that the core uses the compiler's bool type if one exists.
This avoids potential problems of clashes between perl's own implementation
of bool and the compiler's bool type, which otherwise occur when one
attempts to include headers which in turn include <stdbool.h>.
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
| |
|
|
|
|
| |
Work initiated by Tony Cook
|
|
|
|
|
|
|
| |
1. re-generate Configure and config_h.SH
2. update Porting/config_H, which was very outdated
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
|
|
|
|
|
| |
They might have served a purpose in the original files, but Nicholas
and Zefram expressed their concern that in the generated files, these
tags are misleading and unneeded.
|
| |
|
|
|
|
| |
Sorry for the huge config_h.SH re-order. Don't know (yet) what caused that
|
|
|
|
|
|
|
| |
All these files used to be executable in the release tarballs. Apparently things
also work without that in the repository, but I'd rather add this possibly
unecessary change to blead instead of breaking the upcoming release. This should
probably be looked into again afterwards.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When porting/makerel runs, all files copied into the directory for the
tarball have the executable bit stripped and then only a specific set of
files have the executable bit restored.
There are many files in the repo that have the executable bit set in the
repo that will be stripped. So that the state of files in the repo is
as close as possible to the state of files in the release tarball, the
executable bit has been stripped from such files.
In one recent case, a file added from a dual-life module needed the
executable bit set. Because it had the bit in the repo but was
not listed in makerel to get an executable bit, tests using it
passed in the repo and failed in the tarball.
This commit refactors the list into a new file, Porting/exec-bit.txt
and add tests to detect a mismatch between files listed there
and actual executable bits in the repo.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch enables Configure to probe for C99-style 'static inline'.
(That is, functions may be inlined, but will not be externally visible.)
The initial idea is that some common code in messy macros inside headers
might be simplified using inline functions. If the compiler does not
support 'static inline', then a plain 'static' is used instead, along
with the consequent implications of a function call (though the compiler
may optimize away the function call and inline the function anyway).
In either case, you simply use PERL_STATIC_INLINE.
This patch does not *use* this facility at all yet. It is merely a
Configure patch to make the facility availble for others to experiment
with.
VMS and Windows files will still need to be manually updated.
Finally, before actually converting anything to inline functions, please
try to carefully evaluate the performance implications of any proposed
changes. Compilers vary in what they will and will not convert to inline
functions, so it's worth proceeding slowly and carefully.
This patch results from a single new metaconfig unit, d_static_inline.U,
which I will separately upload to the metaconfig repository.
|
| |
|
|
|
|
|
|
| |
Regenerated after backporting 88a6f4fc380d30c40
Please *do* remember to notify the metaconfig folk when directly patching Configure
Bring back Missing parts
|
| |
|
|
|
|
|
|
|
|
| |
Other OS parts will follow
From: Steve Peters <steve@fisharerojo.org>
Date: Wed, 25 Mar 2009 10:54:51 -0500
Message-ID: <fd7a59d30903250854q53311f48o6744df7cbfa1d03d@mail.gmail.com>
|
|
|
|
| |
Backported assorted changes and regenerated Configure
|
|
|
|
|
|
| |
From: "Rafael Garcia-Suarez" <rgarciasuarez@gmail.com>
Message-ID: <b77c1dce0812030351j33d7b75ci3e2640b33f36acd9@mail.gmail.com>
p4raw-id: //depot/perl@34994
|
|
|
|
|
|
|
|
|
|
|
|
| |
From: Nicholas Clark <nick@ccl4.org>
Date: Thu, 27 Nov 2008 20:28:08 +0000
Message-ID: <20081127202807.GG49335@plum.flirble.org>
Subject: Avoid duplicate vendorlib [PATCH]
From: Gisle Aas <gisle@activestate.com>
Date: Wed, 12 Nov 2008 13:50:34 +0100
Message-Id: <71B06786-4C55-4A76-BE24-C01F89015D45@activestate.com>
p4raw-id: //depot/perl@34950
|
|
|
|
|
| |
Message-ID: <20081103224011.26c223b3@r2d2>
p4raw-id: //depot/perl@34756
|
|
|
|
|
| |
Add missing config vars
p4raw-id: //depot/perl@34456
|
|
|
| |
p4raw-id: //depot/perl@34363
|
|
|
| |
p4raw-id: //depot/perl@34107
|
|
|
| |
p4raw-id: //depot/perl@34105
|
|
|
|
|
| |
Removed all files that are now identical to dist-3.5
p4raw-id: //depot/perl@34064
|
|
|
|
|
| |
Message-ID: <Pine.LNX.4.64.0805131224130.9728@fractal.phys.lafayette.edu>
p4raw-id: //depot/perl@33845
|
|
|
|
|
|
|
|
| |
Message-Id: <3B7752C8-D5A2-452C-B3E0-C453FFCBCAFA@mac.com>
[but rename ******* to i_mallocmalloc.U, and then fix up all the files
that Porting/checkcfgvar.pl says need i_mallocmalloc declared]
p4raw-id: //depot/perl@33598
|
|
|
| |
p4raw-id: //depot/perl@33547
|
|
|
| |
p4raw-id: //depot/perl@33321
|
|
|
|
|
|
|
|
| |
loss warning on ++ and -- by moving the check to Configure time,
creating a new config.sh variable nv_overflows_integers_at which
contains an constant expression for the value of the NV which can't
be incremented by 1.0
p4raw-id: //depot/perl@33049
|
|
|
| |
p4raw-id: //depot/perl@33045
|
|
|
| |
p4raw-id: //depot/perl@33038
|
|
|
|
|
| |
is now backported
p4raw-id: //depot/perl@32974
|
|
|
|
|
|
|
|
|
| |
Message-Id: <F4AC553F-7C7F-49C3-98C2-E04681E1004F@hexten.net>
with fixups as discussed on list, plus adding usedtrace to Glossary,
plus propagating all the new config variables everywhere.
(Was there an automatic way to do that? I did it with emacs macros)
p4raw-id: //depot/perl@32953
|
|
|
| |
p4raw-id: //depot/perl@32773
|
|
|
| |
p4raw-id: //depot/perl@32705
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510712110612o7bc5fa2ax9e575c0396cb2a64@mail.gmail.com>
p4raw-id: //depot/perl@32607
|
|
|
|
|
|
| |
2. Regen after backports
3. Include Jarkko's $run and \n patch
p4raw-id: //depot/perl@30977
|
|
|
| |
p4raw-id: //depot/perl@30327
|
|
|
|
|
|
|
| |
comparison)
Message-ID: <Pine.LNX.4.62.0702091121400.10202@fractal.phys.lafayette.edu>
p4raw-id: //depot/perl@30192
|
|
|
| |
p4raw-id: //depot/perl@29467
|
|
|
|
|
|
| |
Subject: [PATCH 5.8.8] Build on OS/2
Message-ID: <20061128113629.GA18108@powdermilk.math.berkeley.edu>
p4raw-id: //depot/perl@29407
|
|
|
| |
p4raw-id: //depot/perl@29338
|
|
|
|
|
| |
2. d_printf_format_null, based on a patch by Robin Barker
p4raw-id: //depot/perl@29288
|
|
|
|
|
|
| |
From: "Steve Peters" <steve.peters@gmail.com>
Message-ID: <fd7a59d30611042340p5543442ctad306aeb748b6bfe@mail.gmail.com>
p4raw-id: //depot/perl@29238
|
|
|
|
|
| |
Plus forced Glossary entry. That is a TODO for automation
p4raw-id: //depot/perl@29213
|
|
|
|
|
|
| |
From: "Benjamin Holzman" <bholzman@longitude.com>
Message-ID: <010801c6ab24$09b9ed30$ce0515ac@office.iseoptions.com>
p4raw-id: //depot/perl@29209
|
|
|
|
|
| |
Configure won't handle versions 5.10.0 or 5.8.10.
p4raw-id: //depot/perl@29096
|