Perl DBI
Skot
Perl5.005 and gcc 2.95.2. perl Makefile.PL says everything is fine, but make
gives me these errors:
/usr/bin/perl -I/usr/local/lib/perl5/5.00503/i386-sco -I/usr/local/lib/perl5/5.00503
/usr/local/lib/perl5/5.00503/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.00503/ExtUtils/typemap
Perl.xs >xstmp.c && mv xstmp.c Perl.c
cc -c -U M_XENIX -D PERL_SCO -D PERL_SCO5 -w0 -belf -I/usr/local/include -O0
-DVERSION=\"1.19\" -DXS_VERSION=\"1.19\" -Kpic -I/usr/local/lib/perl5/5.00503/i
386-sco/CORE -DDBI_NO_THREADS Perl.c
cc: unrecognized option `-w0'
cc: unrecognized option `-Kpic'
cpp: -lang-c: linker input file unused since linking not done
cc: installation problem, cannot exec `cc1': No such file or directory
cc: file path prefix `/usr/local/lib/gcc-lib/elf/2.95.2/' never used
make: *** [Perl.o] Error 1
Anyone know what I'm missing?
TIA.
Skot.
Lukasz Wiechec
I've managed to compile and install successfully Perl DBI on OS 5.0.4 using
gcc 2.7.2.3 (old Skunkware).
Are you sure you are compiling using gcc ? For me it seems you're using
SCO native 'cc', which lacks such options as -w0 or -Kpic. Look into
your 'Makefile' and change 'CC' settings to CC=gcc.
I don't remember exactly what I did (I compiled it about a year ago), but
all you have to do is to make sure you're using proper compiler (i.e. gcc)
and use proper options for it.
Let us know how it went.
--
Milego dnia,
Lukasz Wiechec
Scott Taylor
That wasn't it either. Now I get the same errors but replace the cc
with gcc. I never had cc installed on this server, only ever added gcc.
root@orion:DBI-1.19> cc -v
Reading specs from
/usr/local/lib/gcc-lib/i386-pc-sco3.2v5.0.5/2.95.2/specs
gcc version 2.95.2 19991024 (release)
(I wasn't making it up when I said I was using gcc 2.95.2)
This machine always had strange compiler problems, none that I have seen
on my other OSR5.0.5 machines, but I didn't build this one either. :(
Thanks for trying though.
--
When people find a man of the most distinguished abilities as a writer
their inferior while he is with them, it must be highly gratifying to
them.
-Samuel Johnson
Lukasz Wiechec
> That wasn't it either. Now I get the same errors but replace the cc
> with gcc. I never had cc installed on this server, only ever added gcc.
> root@orion:DBI-1.19> cc -v
> Reading specs from
> /usr/local/lib/gcc-lib/i386-pc-sco3.2v5.0.5/2.95.2/specs
> gcc version 2.95.2 19991024 (release)
> (I wasn't making it up when I said I was using gcc 2.95.2)
Scott, I think you *are* able to compile DBI on your machine. It would
involve some playing aroung with 'Makefile' file -- try to determine
whether your compiler know about all the options, about shared libraries
etc. It took me a while, but it payed off manifold !! :-)
(Yep, I believe you are using gcc 2.95.2 :-))
Greets from Poland,
J. L. Schilling
Your set-up is odd. You're using the cc command to get at the GCC compiler,
when normally Skunkware GCC would install this as the gcc command. Your
configure process has seen the "cc" and decided that you are using the
SCO OpenServer DevSys compiler, and generated options for that compiler
(-w0, -belf, -Kpic) that make no sense for gcc; that's what's responsible
for all the errors you're getting.
Since you are using gcc (which is the right choice for this), you should
fix whatever went wrong in the configure process, such that the build is
done using proper gcc options.
Jonathan Schilling
Skot
You are right, it is an odd setup. Well, this thing never had 'cc'
installed ever. I installed gcc on it a few months ago and it compiled
other things just fine, but something is still wrong with it. BTW, cc
is a symlink to gcc as the gcc install from Skunkware created. I have
tried replacing the 'cc' commands in the makefile (make file) with 'gcc'
and still get the same error message, just swap the 'cc' with 'gcc' and
the messages are identical.
So what do I need to do to fix gcc? What am I missing?
TIA.
Skot
http://www.zenez.com/cgi-bin/scoprogfaq/faq.pl
It fixed now.
Cheers Boyd.
Brian K. White
you missed his point.
since you created a link to gcc named cc, something in ./configure decided
"oh, this system has cc, so I'll generate a makefile that has cc and cc
options."
You need to remove the cc symlink, remove config.cache, and re reun
./configure and hopefully this time the config process will say to itself
"oh this guy doesn't have cc, lets see if he has gcc..."
usually the test is only a very simple test where it just tries to compile a
tiny c program using "cc" with no options. if it succeeds it decides you
have a working cc. It then proceeds to create a makefile that has "cc"
commands and more importantly "cc" command line options that gcc does not
understand.You have misled it into doing the wrong thing.
You need to get it to create a makefile that has compiler command line
options that gcc understands.
you can look in config.log to see what's everything the config process tried
to do in order to arrive at it's decisions about the state of your system.
--
Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
>
> TIA.