| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Under GNU make, an interaction between the top-level 'make -j N harness'
and a make invoked by cpan/ExtUtils-Constant/t/Constant.t
causes warnings like:
warning: jobserver unavailable: using -j1. Add `+' to parent make rule.
Fix this by stopping MAKEFLAGS being inherited by the children.
The other option, of prefixing all the '$(RUN_TESTS) choose' lines
in Makefile.SH with '+' is, I suspect, not portable.
|
|
|
|
|
|
|
|
|
|
| |
runtests is typically run under /bin/sh. If the user uses a different
interactive shell (such as /bin/ksh) that maintains the PWD environment
variable, but /bin/sh does not, then the 'cd t' line in runtests ends
up changing the working directory without updating $PWD. Several tests
in t/io/fs.t rely on being able to change directories and then get back
to the original. The tests assume that if $PWD is set at all, then
it is set correctly. This fix changes runtests to ensure it is so.
|
|
|
|
|
| |
At this point, there are no functional changes. This just prepares
the way for future work.
|
|
|
|
|
|
| |
Whatever the executable is named at the top level, it's always symlinked
as ./perl in t, so there's no need to set an environment variable to
override the expected name.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
But not in the way it was done before with a recursive call to $(MAKE) -
instead create it directly in the current make invocation as an action for
test_prep, and create the link for perl.third directly as an action for
test_prep.third
Also, make it optional to pass the perl to run into runtests, by providing a
default of ./perl$(EXE_EXT)
This feels simpler and still Don't Repeat Yourself.
|
|
|
|
|
| |
Annoyingly bash just accepts it, and dash generates a diagnostic to stderr
but carries on, hence why I didn't spot the problem initially.
|
|
This avoids a recursive call to $(MAKE) in the top level directory, which feels
over-complicated when all the targets invoked have no dependencies.
|