| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This is primarily for pedantic builds; ptrdiff_t is now standard,
and had already been in use in the core without guards.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The final i_bfd statement was a wrong copy-paste
re-order Configure: in preparation of backporting this change and
integration of another, some reorder is required
|
| |
|
|
|
|
|
|
| |
Useful for at least debugging.
Supported in Linux and OS X (possibly to some extent in *BSD).
See perlhacktips for details.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In OS X (and assumedly *BSD) Configure output starts with:
grep empty(sub)expression
apparently because plain 'grep' understands the 'os\(/\|\)2'
somewhat differently (BRE vs ERE, RTFM re_format(7))
Cure: redirect the stderr of grep to stdout (which is then promptly
redirected to /dev/null). The grep will still fail, and not take
the OS/2 (or DJGPP) branch.
|
| | |
|
| |
|
|
| |
Patch by Tony Cook
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
At the "Perl5 and beyond" hackathon early feb 2014 in Amsterdam, hugmeir
and I walked through all the changes and ended up with a serious warning
in metalint where we stopped. The warning proved to be a bug in metalint
that will be fixed in the future and has a rather easy workaround.
Porting/Glossary is not yet being generated correctly. Will take care of
that later.
|
| | |
|
| |
|
|
|
| |
Currently this is only used during make test, and allows setting
the environment of the target before running tests.
|
| |
|
|
|
|
| |
This only required some minor changes to the Solaris hints, and
adding a few lines for Solaris in the part of Configure that handles
setting osname and osvers when cross-compiling.
|
| |
|
|
|
| |
Now, like with Android and plain Linux, cross-compiling to QNX (which
includes newer Blackberry devices) will load hints/qnx.sh.
|
| |
|
|
|
|
| |
Second attempt at this. This is less portable than the previous
version, since it assumes that the target system will have a cat, but unlike
the previous version this now actually works.
|
| |
|
|
|
|
| |
Something like arm-linux-gnueabihf -- which is what the raspberry pi
gets as its targetarch -- is really just plain Linux, so set osname
to that and load up the hints file.
|
| |
|
|
|
|
|
|
|
|
|
| |
When cross-compiling, for android, anything matching *linux-android*
gets osname=linux-androideabi. This is to allow compiling to
all three android variants (x86, arm, mips).
For QNX Neutrino, anything matching nto*|*-nto-* gets osname=nto. In
the future, that might change to 'qnx', but right now we don't want
it to pick up the hints file.
For anything else, keep the current behavior, which is to set osname
to the output of `echo $targetarch|sed 's,^[^-]*-,,'`
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This is because, for example, on the host system, sh might be /bin/sh,
but on the target system, it's /system/bin/sh.
The new variable is "targetsh" and defaults to "sh" unless changed by the hints file/Configure params.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a bit of a step backwards, but we want to run this in
the target platform when cross-compiling to some unusual setups,
like ASCII -> EBCDIC.
What this branch introduces is a third "path" for generate_uudmap:
* If we are doing a native build, just build it as usual and run it.
* If we're cross-compiling, and either -Dhostgenerate was specified OR
if it was left empty, which is the default case, then create
a host generate_uudmap and run it locally
* Finally, if are cross-compiling and were built with -Uhostgenerate,
then build generate_uudmap for the target and run it there, bringing
back the resulting headers.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Previous, if run-ssh was passed ./TEST, it would've ended up running
././TEST in the target system. Similarly, if you passed 'uname',
it would've tried running ./uname, which would've failed
spectacularly.
This commit changes run-ssh so that it won't add the extra './';
this means that shell builtins can be run in the target system.
While this is not generally portable, it's useful in specific
situations, such as in the hints files.
|
| | |
|
| | |
|
| |
|
|
| |
local use
|
| | |
|
| |
|
|
|
| |
See http://www.nntp.perl.org/group/perl.perl5.porters/2012/12/msg196443.html
"Cross-building and Makefile.SH", which explains the reasoning for this.
|
| |
|
|
| |
Do this regardless of whether we are cross compiling
|
| |
|
|
|
|
|
| |
Beyond organization, this also makes sure that usecrosscompile is
always set to undef if we're not cross-compiling, which enables
code to realibly use $Config{usecrosscompile} to check for a
cross-compiling perl.
|
| |
|
|
|
| |
I am sure there are items that could have been processed even cleaner,
but with the current state, the content is functional equal.
|
| | |
|
| |
|
|
|
| |
Such as when using user networking on qemu and redirecting a local port
to the emulator ssh
|
| | |
|
| |
|
|
| |
This doesn't seem to be of much use.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
If the user specified -Dsysroot but we don't use it, then the results can
be entirely off.
This also introduces an internal variable for Configure, _sysroot,
which is just "--sysroot=$sysroot", for use in places like checkccflags that
need --sysroot but don't need the other flags.
|
| |
|
|
|
| |
This skip was added in 2001, but under the current model there's no
real reason to skip it.
|
| | |
|
| |
|
|
|
|
| |
Ditto with g++. This allows us to use, for example, ntox86-gcc or
x86_64-w64-mingw32-g++.exe to cross-compile, and have Configure detect
most things automatically.
|
| |
|
|
|
| |
This means that osnames that look like *linux*, like linux-androideabi
or linux-gnueabihf are treated like linux systems.
|
