| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
3b28d668e9efe9433c3099521167a6723cbddc26 depended on command-line
specification of usethreads, which of course may not be there.
|
|
|
|
|
|
| |
It's hard-wired in perl.h, so it doesn't make any difference to
what's seen by the C code, but $Config{multiplicity} should reflect
what we're actually doing (and track what Configure does).
|
|
|
|
|
|
|
|
|
|
| |
Now that we have the relevant questions answered before we set
archname, add the appropriate components to archname at the right
time so they'll become part of the architecture-specific
directory names.
FIXME: We don't (yet) set archname64, so at present we're not
adding it to archname.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By moving these to after other questions have been asked, we can
construct a proper $Config{archname} that indicates threads, long
doubles, multiplicity, or anything else that needs to be appended
to the architecture name.
This means letting go of the ability to configure for a different
architecture than the one you're running on, but that feature is
unlikely to have worked very well in recent years anyway as there
have been an increasing number of features that are not available
on all architectures.
|
|
|
|
|
|
|
|
|
| |
We were only using the base archname (e.g., "VMS_AXP"), which is
ok for a default bulid, but if any additions were made to it,
such as "-thread", there would be a discrepancy between the
actual directory on disk and what perl.c:S_incpush would look for
when loading up @INC. The net effect was that the architecture-
specific directory would not get loaded into @INC.
|
|
|
|
|
|
|
| |
Instead of testing for equality, look for the first minus sign-
delimited element. This means it won't matter which order these
checks are done in relation to adding things like "-thread-multi"
to archname.
|
|
|
|
|
| |
It's present on recent versions, but not all versions. Follow-up
to f53580fec42f3b12264ee27b756dec257c0bb77a.
|
| |
|
|
|
|
|
| |
It's available on anything decent and recent, but it requires
_SOCKADDR_LEN defined to make it visible.
|
|
|
|
| |
Sorry for the huge config_h.SH re-order. Don't know (yet) what caused that
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
* important changes in version 1.70 15/11/2010
- Add ptargrep utility courtesy of Grant McLean
** I think I found everywhere that needed updating
by grepping for 'ptardiff' and adding where needed.
This stuff is definitively not intuitive.
|
|
|
|
|
|
|
|
|
| |
It used to be that once or twice per decade a symbol longer than
31 characters snuck into the core and we had to manually shorten
it to get the build working. But it's happened twice in the last
month, most recently with the humanly unswallowable function name
XS_XS__APItest__XSUB_XS_VERSION_undef, so the need for a more
general solution has become not only apparent but mandatory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Traditionally Perl does its own name shortening in
ExtUtils::XSSymSet to get around the 31-character limit
on symbol names in the VMS linker. That method predates
the availability of the /NAMES=SHORTENED option in the
C compiler, which uses the same algorithm as the C++
name mangler to produce shortened symbols. This change
makes configuration with -Duseshortenedsymbols select
the compiler's shortening over the home-grown shortening.
The advantages of the compiler option over the home-grown
option are that hand-coded long symbols in the core can be
handled (instead of only generated XS_... symbols); long
symbols in external libraries can be handled; and eventually
we can remove XSSymSet and have less to maintain.
84efe3dfc6afbd8ea017ddcc4d5d213cc1a35c72 is required to travel
wherever this change travels for extension building to work
properly.
|
|
|
|
|
| |
This assumes all VMS compilers that build perl will
support 'static inline'.
|
|
|
|
|
| |
Formerly it only worked if you went through all the questions
interactively and explicitly answered no.
|
|
|
|
|
|
| |
DCL symbol length was limited to 1K up until about seven years or
so ago, but there was no particularly deep reason to prevent those
older systems from configuring and building Perl.
|
|
|
|
| |
This was missing from c796e3db23c597b99f07485542338844e61a6a69
|
|
|
|
|
| |
Follow-up to d03b3b00ac22f32af87a752669a46d9d06ae1561, which broke
the build.
|
|
|
|
|
|
|
| |
Like it has been everywhere else for ages and ages. Also make
command-line selection of -UDEBUGGING and -DDEBUGGING work in
configure.com; before the only way to turn it off was by saying
no in answer to the interactive question.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to Carl Friedberg for the suggestion.
|
| |
|
|
|
|
| |
Needs checking
|
|
|
|
| |
accordingly.
|
| |
|
|
|
|
| |
But thanks for 7 1/2 years of faithful service.
|
|
|
|
|
|
|
| |
Revised slightly and the effects of dash versus slash changed in the
list of exclusions.
Message-ID: <20090206211641.GA39741@plum.flirble.org>
|
| |
|
| |
|
|
|
|
| |
Partially based on suggestions from John Malmberg at <495C279C.7020106@gmail.com>.
|
|
|
|
|
|
| |
From: "Rafael Garcia-Suarez" <rgarciasuarez@gmail.com>
Message-ID: <b77c1dce0812030351j33d7b75ci3e2640b33f36acd9@mail.gmail.com>
p4raw-id: //depot/perl@34994
|
|
|
| |
p4raw-id: //depot/perl@34952
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
| |
p4raw-id: //depot/perl@34771
|
|
|
|
|
| |
on Bar.pm~ at MANIFEST check time when building on an ODS-2 volume.
p4raw-id: //depot/perl@34561
|
|
|
|
|
| |
Add missing config vars
p4raw-id: //depot/perl@34456
|
|
|
| |
p4raw-id: //depot/perl@34131
|
|
|
|
|
| |
Message-ID: <Pine.LNX.4.64.0805291241070.365@fractal.phys.lafayette.edu>
p4raw-id: //depot/perl@33949
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
what Configure does). Problem using long int without long double
reported by Jeremy Begg.
p4raw-id: //depot/perl@33591
|
|
|
|
|
|
| |
From: "John E. Malmberg" <wb8tyw@qsl.net>
Message-id: <47E6AF95.1000704@qsl.net>
p4raw-id: //depot/perl@33550
|
|
|
|
|
|
| |
as 33431 should have done (and would have if I'd remembered to
remove --dry-run from the patch command).
p4raw-id: //depot/perl@33438
|
|
|
| |
p4raw-id: //depot/perl@33275
|
|
|
|
|
|
|
|
| |
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
|