Martin J. Evans wrote:
Perhaps I am misreading
http://www.nntp.perl.org/group/perl.cpan.testers/2009/01/msg3090019.html
but it looks as if the C compiler is not set up properly. Why would
anyone be smoking and attempting to build XS modules without their C
compiler being set up. May be this is some other issue. Any ideas?
Martin
I am somewhat surprised the way the discussion went on this thread. Just
to clear a few things up from my perspective.
As Jan Dubois says, the error messages referred to in the smoke report
do appear to be from the Perl DBI module (actually, they are in
DBI::DBD) - I didn't realise that but in any case it was not my point.
My point was it looked like someone was smoking XS modules without a
properly installed development system capable of compiling and linking C
code. I guessed that from the aforesaid message that DBI::DBD output
which I think is a good message.
It would appear some people think it is perfectly reasonable to smoke XS
modules without a supporting development system - that's fine, I don't
really see the point myself but I can live with it.
All I was really attempting to do was to a) confirm that someone was
smoking without a development system and b) try and find out why. It
could always have been a problem in my module, and that was what
definitely did concern me.
I don't really have any strong opinion on the later discussions over
whether cc is in $Config{cc} but I would simply make one point. It is a
regular occurrence on the dbi-users list for someone to install a Perl
binary they got from IBM/Sun/HP/etc/etc and then try and use a compiler
different from the one used to build Perl - it never seems to work
(unsurprisingly). I often wonder why this is never caught. Lately, a new
issue is taking over - someone installs a 32bit perl and attempts to use
it with 64bit libraries or vice versa.
Thank you to all who responded.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
