| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
uudmap.h is created first, so bitcount.h should depend on it
rather than vice versa. Correcting this avoids unnecessary
recompiles of globals.c.
|
| |
|
|
|
|
|
| |
This way patches including perldelta entries will apply properly, no matter when
they are applied. If there's conflicts, they'll at least be in the right file.
|
|
|
|
|
| |
Follow-up to 6999193ba9069e620831bed0f85efa43ff6e283a, which broke
the build on VMS because the rule to build uudmap.h was unknown.
|
|
|
|
|
| |
The fixes of Makefile.SH in 0f13ebd5d71f8177 also need to be applied on Win32
and VMS.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
In Perl_rename() we were allocating the same thing twice.
In vms_fid_to_name() (used by realpath() and realname()), we had
another flagrant omission of freeing local storage.
|
|
|
|
|
|
|
|
| |
Thanks to Mark Berryman in
Message-id: <52BFD39B-C4BA-4350-AA1F-C2E7F128EF21@theberrymans.com>
for the report and the fix.
|
| |
|
|
|
|
|
| |
Cherry picking this from 5.12.1 would lose all the 5.13.X additions, so
these edits have been made by hand.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The prototypes removed here, while in some ways superior to those
provided in the system-supplied headers, in other ways conflict
with them. The conflicts were masked in the default build by the
fact that the macros mapping lower case names to upper case were
undefined, so at compile time there were really two different
prototypes even though at link time the symbols were the same.
But the conflict broke the build when compiling with /NAMES=AS_IS
to preserve symbol name case. Overall, whatever modest benefit
maintaining our own prototypes might provide, it's just not worth
the risk of conflict. A better approach would be to define
__NEW_STARLET and work through whatever the compiler complains
about.
For sys$sigprc and lib$initialize, we do continue to provide our
own prototypes (and add lower case to upper case mapping macros)
because there are no system-supplied prototypes for them.
|
|
|
|
|
| |
This was an oversight in 5.12.0 and without it some extension builds
fail.
|
| |
|
| |
|
|
|
|
|
| |
We were checking a variable that doesn't exist in the non-default
case of disabling perlio. Now we only look at it when it exists.
|
| |
|
| |
|
|
|
|
| |
Thanks to Ask for pointing it out.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
As Charles Lane's piping code reaches its 10-year anniversary, it's
time to bump up the default to something slightly more appropriate
for modern systems. In addition to other benefits, this fixes test
failures when a test script outputs a large amount of text on one
line (e.g., t/re/reg_posixcc.t).
|
|
|
|
| |
Message-ID: <4B0C4744.7080401@khwilliamson.com>
|
| |
|
| |
|
|
|
|
|
| |
Don't use register storage class for something we later take the
address of.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It can't really be renamed from ext/Cwd to ext/PathTools, because Configure and
Makefile.SH need to know the name of the shared object produced, and they infer
this from the name of the directory.
This concludes the migration of modules from lib to ext. Exporter and version
remain in lib, but I don't think that there is any benefit in trying to move
either of them.
|
|
|
|
|
| |
Nothing up to and including minitest uses lib, and not needing many special
case rules to extract from lib/lib_pm.PL simplifies all the Makefiles.
|
| |
|
|
|
|
|
|
|
| |
But not the tests yet.
We need to avoid running a sitecustomize script as it may have side effects
that cause the build to fail, or worse, complete but with buggy side effects.
|
|
|
|
| |
lost in disentangling previous commit.
|
|
|
|
|
|
| |
This reverts commit 052792984b8f177f8f314261429d93930437fc49.
We do actually need both -"I[.lib" and -"I[-.lib]"
|
|
|
|
|
|
| |
403f501d5b37ebf0340212b1a7f7c01855cd7b95.
In preparation for reverting 052792984b8f177f8f314261429d93930437fc49.
|
| |
|
|
|
|
|
| |
Obviously, it's going to take a bit more work to piece the PathTools
distribution back together.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It seems that the code in the Makefile to run AutoSplit over lib has actually
been vestigial since some point *before* 5.000. Presumably, initially, Perl code
for extensions was in lib, and autosplit (the precursor to AutoSplit.pm) was run
on them there. Or they were copied from ext to lib first, before splitting.
Fifteen year-old backup tapes refuse to give us the detailed history of the
pre-5.000 period.
Whatever the cause, the code was never needed - backed up by the absense of any
analgous code in the Win32 Makefiles. So remove it. This happens to also remove
the only use of the shell script makedir, so remove it too.
|
| |
|
|
|
|
| |
Introduced in d1a2168615d31496c65bd27adf6b78d44834861c.
|