----- Original Message ----- From: "Nicholas Clark" <[EMAIL PROTECTED]> . . > > IIRC 5.8.8 itself shipped with something sufficiently broken in one of the > headers such that g++ can't compile perl extensions.
Could be the problem, then - though there's no such problem with the MinGW port of g++ on Win32, perl 5.8.8 (built from official perl source using MinGW's gcc and dmake). > I don't think that it > was actually noticed until a month or so after the release, and this is only > the second time I can remember anyone reporting the problem. > Given the amount of time I spend on linux, and the amount of time I spend with C++ code, it's about a "one in a million" chance that I came across it :-) > The release candidate also had this problem. I can't spot everything, and if > almost no-one tests the release candidate (let alone any maint snapshots) > then mistakes like this will happen. > Quite so. I've just now installed bleadperl (5.9.3) on the linux box, and the same behaviour occurs. I can actually provide a small source distro (based on the 01nherit.t Inline::CPP test script) that demonstrates my g++ problem. This particular source distro has no dependence on Inline in any way, builds fine on Win32, but won't build on Linux - with either 5.8.8 or 5.9.3, instead producing essentially the same errors as I reported in my initial post. Actually it's only a smallc distro, so I'll attach it with this post. (It assumes the compiler being used is 'g++' - otherwise you'll have to modfiy the Makefile.PL.) If the error can be reproduced elsewhere, then I guess we're looking at a bug ... otherwise it's probably just that there's something screwed on my linux box .... and it's certainly not up to anyone on this list to help out with that :-) > I'm surprised that Mandriva don't ship a perl tweaked to fix this. > They may do that, faik. I don't run linux all that much - it's mainly for comparison (with Win32) purposes. Thanks for the reply, Nicholas. Cheers, Rob
FooBar.tar.gz
Description: Binary data
