[ILUG] RE: GCC and perl

[Conor Daly]

On Thu, Jul 26, 2001 at 04:27:04PM +0100 or thereabouts, Barry Carroll wrote:
> thanks to all so far....
> 
> what I did since was to go into the source and give the paths in all
> the #include statements. The paths are correct.
> 
> eg: #include "/usr/libdata/perl/5.00503/mach/CORE/EXTERN.h"
> 
> then i invoke gcc:  gcc -v -o test2exe test2.pl.c
> 
> It generated the object file, so is this a linking error?
> 
> [first 4 errors}
> /tmp/cc1btNUh.o: In function `perl_init':
> /tmp/cc1btNUh.o(.text+0x17): undefined reference to `Perl_av_extend'
> /tmp/cc1btNUh.o(.text+0x2d): undefined reference to `PL_sv_undef'
> /tmp/cc1btNUh.o(.text+0x68): etc etc
> 
> I get this same type of error even if i leave the source alone
> and invoke gcc as follows:
> 
> gcc -v -o test2 test2.pl.c -I/usr/libdata/perl/5.00503/mach/CORE/

Did your original #includes look like:

#include "EXTERN.h"

or 

#include<EXTERN.h>

?

AFAIK, (#include<lib.h>) will look in any lib paths for lib.h while
(#include "lib.h") will look only in the current directory.  So,

#include<EXTERN.h>

and 

gcc -v -o test2 test2.pl.c -I/usr/libdata/perl/5.00503/mach/CORE/

should work unless the lib path from the commandline after the inbuilt one.

Conor
-- 
Conor Daly 
Met Eireann, Glasnevin Hill, Dublin 9, Ireland
Ph +353 1 8064276 Fax +353 1 8064275
------------------------------------
  4:11pm  up 63 days,  3:14, 10 users,  load average: 2.05, 2.05, 2.09