Am 03.06.2014 um 01:42 schrieb David Golden <x...@xdg.me>: > On Mon, Jun 2, 2014 at 7:28 PM, Aristotle Pagaltzis <pagalt...@gmx.de> wrote: >> If I have my system set up to support XS then I want it to use XS, and >> if for some reason it can’t, then there is a bug somewhere that needs to >> be fixed, so I do *not* want it to silently give me the PP version and >> carry on, but to fall down and die screaming so I’ll find out. > > I've been trying to think of how that could happen and so far all I > can come up with is this scenario: > > * XS bits compile successfully, but the shared object croaks during > bootstrap, and the calling module traps the bootstrap error and falls > back to PP
There're several scenarios causing XS builds to fail: 1) compiler cannot create executables * invalid cflags configured (see http://www.cpantesters.org/cpan/report/a25a36da-ea1d-11e3-9cf0-a01f06268b4b for an example) * beta compiler test (sunpro 12.4 on linux fails loading libdwarf) * cc installed, but as missing 2) compiler works, but no perl headers 3) compiler does, but shared library building fails (that is fragile and minor modifications at the system causes that process to fail) 4) As you say: https://rt.cpan.org/Ticket/Display.html?id=75672 I think currently we don't cross-compile (handy market would make me want to change that), which allows tests for 4, but until 3 we can always test. 4 only when we don't cross-compile. And what does "I prepared my system to support XS" mean? I installed a compiler or I installed precisely the same compiler/binutils used to build perl? I think, there should be a flag the user to be able to set to express the opinion the system is prepared for XS - not any magic detection. Users word counts. Cheers -- Jens Rehsack rehs...@gmail.com
