Re: "the same compiler that was used..."



Thanks Steve. I've added something along those lines.

Tim.

On Wed, Nov 22, 2006 at 09:24:02AM -0800, Steve Canfield wrote:
Thanks Philip!

This morning before your email arrived it occured to
me that binary Perl modules might be installed through
Synatpic package manager the same way I installed gcc.
For DBI and LWP that turned out to be the case.
Installing libc6-dev (using Synaptic) allowed me to
install the WeakRef perl module. I suspect that
installing libc6-dev would have allowed me to compile
DBI.

So it perhaps the README for DBI could be expanded
just a little. As I read the relevent section, it
appears that there is only one solution to the
problem: recompile Perl. Here's the section in
question:

"If you get compiler errors refering to Perl's own
header files (.../CORE/*.h) or the compiler complains
about bad options etc then there is something wrong
with your installation. It is best to use a Perl that
was built on the system you are trying to use and it's
also important to use the same compiler that was used
to build the Perl you are using."

There may be two other ways to address the problem.
Perhaps something like this would guide people towards
solutions:

"If you installed Perl using a binary distribution,
such as ActiveState Perl, or if Perl came installed
with the operating system you use, such as Debian or
Ubuntu, then you may be able to install a precompiled
binary of DBI using a package manager. Check the
package manager for your distribution of Perl (e.g.
ppm for ActiveState) or for your operating system (e.g
Synaptic for Ubuntu). See [some URL here] for more
information about package managers.

You may also be able to augment your compiler with
[not sure what to put here, perhaps someone in this
mailing list can come up with something]."


--- "Garrett, Philip (MAN-Corporate)"
<Philip.Garrett@xxxxxxxxxxx> wrote:

Steve Canfield wrote:
"the same compiler that was used..."

[snip]

The entirety of the output of "perl Makefile.PL",
"make", and "perl -V" are echoed below. However,
I
believe the problem lies in this error and others
like
it:

/usr/lib/perl/5.8/CORE/perl.h:382:24: error:
sys/types.h: No such file or directory

Looks to me like you need the libdevel/libc6-dev
package:
http://packages.ubuntu.com/edgy/libdevel/libc6-dev

Good luck!

Regards,
Philip



__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
.



Relevant Pages

  • Re: Loading DBI Problem
    ... The C compiler you have 'installed' is a dummy that isn't really ... libraries - installing GCC won't help unless you also compile and ... install your own version of Perl using the GCC you've just installed. ... > make: Fatal error: Command failed for target `Perl.o' ...
    (perl.dbi.users)
  • ANNOUNCE: UnixODBC 0.31
    ... UnixODBC provides a toolkit for writing Perl ODBC clients. ... - Installing and Configuring the Bridge Server ... UnixODBC.pm provides Perl programs with a subset of the X/Open ... Bridge Server," below. ...
    (comp.lang.perl.modules)
  • Re: Install DBI on Solaris
    ... people having this issue and the solutions seem to revolve around ... installing a new compiler, etc. ... install and the perl -V. ... You don't have the correct C compiler on your PATH (maybe, ...
    (perl.dbi.users)
  • RE: "the same compiler that was used..."
    ... Synatpic package manager the same way I installed gcc. ... Installing libc6-dev allowed me to ... install the WeakRef perl module. ... "If you get compiler errors refering to Perl's own ...
    (perl.dbi.users)
  • Re: Unix commands
    ... might have a problem or two with installing some CPAN modules as well. ... Skilled programmers are able to see the ... Then their problem already starts with using Perl on Windows (for ... Most external tools have switches that enable / disable features. ...
    (comp.lang.perl.misc)