| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Handling of the default is done further down.
|
|
|
|
| |
That's it. Dot no longer in @INC.
|
|
|
|
|
|
|
|
| |
dtrace without -xnolibs fails in a FreeBSD jail, so we need to supply
it on FreeBSD.
Unfortunately systemtap's dtrace emulation doesn't support -xnolibs so
we need to test if it's available.
|
|
|
|
|
| |
These are currently zero anyway, but things are probably not guaranteed
to stay so.
|
|
|
|
|
|
|
|
|
| |
The test had several problems that resulted in the excess
bytes not getting zeroed out. This caused random contents in
$Config{longdblinfbytes}, observed on Debian with GCC 6.2.0 (but not
5.4.1).
Bug-Debian: https://bugs.debian.org/844752
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Perl now provides a way to build perl without . in @INC by default. If you want
this feature, you can build with -Ddefault_inc_excludes_dot
Because the testing / make process for perl modules do not function well
with . missing from @INC, Perl now supports the environment variable
PERL_USE_UNSAFE_INC=1 which makes Perl behave as it previously did,
returning . to @INC in all child processes.
WARNING: PERL_USE_UNSAFE_INC has been provided during the perl 5.25 development
cycle and is not guaranteed to function in perl 5.26.
Update unit tests and default value files to work with the new %Config
variable "default_inc_excludes_dot"
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For windows/netware It seems that many of the recent fp definitions
have not been yet copied over there [1] [2], so went mostly by dead
reckoning [3].
[1] Note that many of them are not absolutely necessary for building.
[2] The proper updating involves doing stuff in win32, which I do not have.
[3] As far as I can tell, Windows CE does not really not have long double.
|
|
|
|
|
|
|
| |
It was assuming a negative zero, which is an IEEE-754 only concept.
There is no need to assume the negative zero for the correct
functioning of the signbit, however.
|
|
|
|
|
|
|
|
|
|
|
| |
For completeness: it's quite unlikely Perl would build in those
environments.
Though with Cray it's less impossible: Perl used to build in C90
UNICOS, in 5.8-ish timeframe.
With IBM, highly unlikely, because there probably never was a UNIXy
enough environment where the IBM Floating Point Architecture was used.
|
| |
|
| |
|
|
|
|
| |
(And in VAX, that is exactly what happens with the infinities.)
|
| |
|
| |
|
|
|
|
|
|
| |
This has long been a confusing configure question. It sounds like
it saves time by installing /less/, but really it just installs
binaries with a version number suffix.
|
|
|
|
| |
See [perl #126203]
|
|
|
|
| |
The oxford comma makes no sense in a list of just two
|
|
|
|
| |
Self-explanatory. The code in question adds -quadmath to archname, but only if it isn't already there. However, since this was copied from a few lines earlier, it checks for -ld instead of -quadmath.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Detect the VAX floating point formats D and G.
And the F float, but that is float (duh), never likely to be
the double, but do it for consistency (we detect IEEE single
precision floats, too).
The T float and X float are the IEEE 64-bit and 128-bit,
but those were available only on the Alpha.
Tested on vax-netbsd.
|
|
|
|
|
|
|
|
|
| |
As requested by khw++
Until the relevant symbol is used, HAS_STRERROR_L must be mentioned
explicitly in metaconfig.h.
This corresponds to metaconfig d0838744f03cfe7642950ea91dd48f575d0bfd15.
|
|
|
|
|
|
|
|
|
| |
As requested by khw++
Until the relevant symbol is used, HAS_QUERYLOCALE must be mentioned
explicitly in metaconfig.h.
This corresponds to metaconfig 541f0dd272df4f9326996727898393ac8f6626f7.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Relevant changes:
commit 5d3ffa97290d2d3d65a42a0ed8b69d945b661ee7
Author: H.Merijn Brand - Tux <h.m.brand@xs4all.nl>
Date: Sun May 29 15:30:33 2016 +0200
Finish.U isn't modified anymore
All changes accepted by upstream. One down, 164 to go
commit 5d805d83bd4663831594540ddadeeb6213d19736
Author: H.Merijn Brand - Tux <h.m.brand@xs4all.nl>
Date: Sat May 14 18:48:26 2016 +0200
Remove trailing whitespace on meta-lines in unit files
This change has also been proposed as PR to dist upstream
commit b9807b5fe3f4c97fa34e19b8a9b265f91f0e4aca
Author: H.Merijn Brand - Tux <h.m.brand@xs4all.nl>
Date: Sat May 14 18:30:03 2016 +0200
Merged changes to Finish.U
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 97076f2 added a graceful exit to Configure when targethost is
not defined but usecrosscompile is. However, this is not reached because
there is a similar check a bit earlier that makes Configure bail out.
Make the earlier check warn instead of croaking.
The use case for this combination is supplying an external config.sh
suitable for the target platform, avoiding the need for configuration
probes.
|
|
|
|
|
| |
perl5.git is now in sync with metaconfig.git commit
7c34fa4e8142642c6e2978f0307e925898465f58
|
|
|
|
|
| |
Work done at the QAH in Rugby.
Multi-thanks to Aaron for helping out here. You're doing a great job!
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
When built with -Dusedtrace, Configure checks to see whether 'dtrace -G'
is supported, by running it. If it fails, it may spew error messages
to stderr, so use >/dev/null 2>&1.
|
|
|
|
|
|
|
|
|
| |
On one of the try.c compilations, redirect stderr to /dev/null, since
the code can legitimately warn without there being a problem.
The try.c in question is probing for what symbols the compiler supports.
The clang extensions __has_include and __has_include_next are designed
only to be used in .h files, so they warn if used from try.c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When building the object file, newer versions of dtrace (on Illumos
based systems at least) require an input object file that uses
at least one of the probes defined in the .d file.
The test in Makefile.SH didn't provide that definition so the test
would fail, and not build an object file, and fail to link later on,
on systems that *do* need the object file.
Moved the probe to Configure (where it probably belongs) and supplied
an object file that uses a probe.
Tested successfully on OmniOS (with the new dtrace), Solaris 11,
and darwin.
|
| |
|
|
|
|
|
|
|
|
| |
These are all specified by POSIX/SUSv3, but not all platforms have them,
as mentioned in POSIX.pm.
We can only test the pid, uid and code fields, since they are the only
ones that are defined for a user-sent signal.
|
|
|
|
|
| |
This patch also adjusts the generated files suggested by
Porting/checkcfgvar.pl.
|
|
|
|
|
| |
Nm stood for "New Math" library in the context of 1994. 2014 a conflicting
library libnm appeared that has a network manager context.
|
| |
|
|
|
|
| |
It does not work in SysV (solaris) or old BSD greps.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The ppc64el is the first seen little-endian double-double (and also
the first little-endian ppc), but it turns out its little-endianness
is mixed: the doubles are still in big-endian order. Configure was
expecting wrongly a fully byte-reversed double-double.
Therefore extend the long double format detection to cover all the
(double-double) permutations, though the formats of five and eight
are rather unlikely (based on current platforms using double-double).
|
|
|
|
| |
They can be zero, they can be garbage.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As far as I can tell, using the -S and -O options together has always
yielded an error of this form:
Configure: 2042: .: Can't open ./optdef.sh
That's because, even though optdef.sh is created in the UU directory, and
most of Configure is run in that directory, part of the -S implementation is
run in the root directory, and was therefore trying to read ./optdef.sh
instead of ./UU/optdef.sh.
As of 41d73075f0801c26794dadb1ff690f305d7e53a7, the -O mode is always
enabled, so the -S option has been broken since then. This fixes that.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 821805a244cacd9869331999cd53407f3323206a.
What's out, is out.
perl #107904 Filesys-Df
perl #108189 Filesys-DfPortable
perl #108191 Filesys-Statvfs
perl #126368 Filesys-DfPortable
|
| |
|
|
|
|
| |
Configure /proc issues, honor d_procselfexe and procselfexe hints.
|
|
|
|
|
|
|
|
|
|
|
| |
This bug has been here since 2001, introduced by yours truly
in 58e77565. Hasn't been too harmful, obviously. It doubles
the cppflags only once, thankfully, unlimited doubling would
probably have been noticed earlier.
The avoidance maneuver is far from fool-proof. To be more
fooler-proofer, some sort of order-preserving deduping would
be needed.
|