http://qs321.pair.com?node_id=586520

shotgunefx has asked for the wisdom of the Perl Monks concerning the following question:

Any thoughts on exactly how to configure C support in Module::Build?

I'm trying to get my carpc-dev system and the car-pc itself in sync as I'm having different issues with both tracks of SDL (2.1.3 & 1.2.3 devsnapshot) and workarounds in one usually causes a problem in the other.

The main reason I'm using two versions is I cannot get 2.1.3 to build on the car system. Module::Build bails complaining that C support is not configured.

Is my perl install broken? I'm loath to change too much on the car system (laptop), because getting everything to work in the first place (SDL,dual-heads, sound, suspend, etc) was a nightmare and something always breaks whenever I upgrade anything.

Here's the info
$Module::Build::VERSION => 0.2805


Summary of my perl5 (revision 5 version 8 subversion 8) configuration: Platform: osname=linux, osvers=2.6.15.4, archname=i486-linux-gnu-thread-mult +i uname='linux ninsei 2.6.15.4 #1 smp preempt mon feb 20 09:48:53 ps +t 2006 i686 gnulinux ' config_args='-Dusethreads -Duselargefiles -Dccflags=-DDEBIAN -Dccc +dlflags=-fPIC -Darchname=i486-linux-gnu -Dprefix=/usr -Dprivlib=/usr/ +share/perl/5.8 -Darchlib=/usr/lib/perl/5.8 -Dvendorprefix=/usr -Dvend +orlib=/usr/share/perl5 -Dvendorarch=/usr/lib/perl5 -Dsiteprefix=/usr/ +local -Dsitelib=/usr/local/share/perl/5.8.8 -Dsitearch=/usr/local/lib +/perl/5.8.8 -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/ma +n3 -Dsiteman1dir=/usr/local/man/man1 -Dsiteman3dir=/usr/local/man/man +3 -Dman1ext=1 -Dman3ext=3perl -Dpager=/usr/bin/sensible-pager -Uafs - +Ud_csh -Uusesfio -Uusenm -Duseshrplib -Dlibperl=libperl.so.5.8.8 -Dd_ +dosuid -des' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemulti +plicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS +-DDEBIAN -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE +_SOURCE -D_FILE_OFFSET_BITS=64', optimize='-O2', cppflags='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBIAN +-fno-strict-aliasing -pipe -I/usr/local/include' ccversion='', gccversion='4.0.3 (Debian 4.0.3-1)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=1 +2 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', + lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='cc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib libs=-lgdbm -lgdbm_compat -ldb -ldl -lm -lpthread -lc -lcrypt perllibs=-ldl -lm -lpthread -lc -lcrypt libc=/lib/libc-2.3.6.so, so=so, useshrplib=true, libperl=libperl.s +o.5.8.8 gnulibc_version='2.3.6' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E' cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP THREADS_HAVE_PIDS USE_ITHREAD +S USE_LARGE_FILES USE_PERLIO USE_REENTRANT_API Built under linux Compiled at Apr 4 2006 22:23:52 @INC: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .
Thanks.

-Lee
"To be civilized is to deny one's nature."

Replies are listed 'Best First'.
Re: Configuring C Support in Module::Build
by Limbic~Region (Chancellor) on Nov 28, 2006 at 17:16 UTC
      That did the trick (kind of), still need to resolve some issues with lib locations. I wonder why ExtUtils::ParseXS isn't referenced in the error. That would have made a lot more sense. I assumed any needed common components for building modules would be installed standard.

      -Lee
      "To be civilized is to deny one's nature."
      Many thanks. If there was a message about it in the build output, I must have missed it.

      -Lee
      "To be civilized is to deny one's nature."
Re: Configuring C Support in Module::Build
by zentara (Archbishop) on Nov 29, 2006 at 13:20 UTC
    I've seen this problem mentioned more than once, it always involves people installing Module::Build thru an automatic cpan install, and missing the message about C support; OR distros which ship a pre-built Module::Build that doesn't have C support. It's why I always build modules manually, even though it takes a few minutes longer. Module::Build clearly stops and prompts for an answer to the question "Enable C support? "

    I'm not really a human, but I play one on earth. Cogito ergo sum a bum