Mail Archives: cygwin/2000/12/16/01:36:38
Steve asks about:
> I'm having problems building the Compress::Zlib 1.08 perl module from
> inside cygwin.
> It appears to be a C compiler problem. The (knowlegable) author of
> Compress says it looks like a cygwin problem.
> I've attached the output of cygcheck -s
>
> Thanks,
> Steve Kelem
>
> -------- Original Message --------
> Subject: RE: problem building Compress::Zlib 1.08
> Date: Wed, 13 Dec 2000 18:12:33 +0000
> From: Paul Marquess <paul_marquess AT yahoo DOT co DOT uk>
> Reply-To: Paul DOT Marquess AT btinternet DOT com
> To: Steve <s_kelem AT pacbell DOT net>
> CC: paul DOT marquess AT btinternet DOT com
>
>
>
> From: Steve [mailto:s_kelem AT pacbell DOT net]
>
> Steve,
>
> I don't do any development on NT, but from the look of the output you've
> sent me it looks like a problem with cygwin.
>
> Paul
Paul's right.
> > I'm having problems compiling Compress::Zlib-1.08 on the latest cygwin
> > under Win NT 4, Sp 6a.
> > I installed zlib 1.1.3.
> > I edited config.in:
> > BUILD_ZLIB = True
> > INCLUDE = /usr/local/include
> > LIB = ../zlib-1.1.3
{snip}
> > Here is the build log for Compress::Zlib
> > % perl Makefile.PL
> > Parsing config.in...
> > Created a Makefile.PL for zlib
> > Building Zlib enabled
> > Looks Good.
{snip}
> > dllwrap --dllname Zlib.dll --driver-name gcc --dlltool dlltool
> > --export-all-symbols --as as --output-def libZlib.def --output-lib
> > libZlib.a \
> > -L/usr/local/lib Zlib.o ../zlib-1.1.3/libz.a
> > /usr/local/lib/perl5/5.6.0/cygwin/CORE/libperl5_6_0.a
> > Warning: no export definition file provided
> > dllwrap will create one, but may not be what you want
# this is definitely where your problem is
> > /H-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/2.95.2/../../../
> > ../i586-cygwin32/bin/ld:
> > Can't open base file /c/TEMP\cc000554.base
# that ^^^^^ was it, the rest was business-as-usual.
> > collect2: ld returned 1 exit status
> > dllwrap: gcc exited with status 1
> > perlld: *** system() failed to execute
> > dllwrap --dllname Zlib.dll --driver-name gcc --dlltool dlltool
> > --export-all-symbols --as as --output-def libZlib.def --output-lib
> > libZlib.a \
> > -L/usr/local/lib Zlib.o ../zlib-1.1.3/libz.a
> > /usr/local/lib/perl5/5.6.0/cygwin/CORE/libperl5_6_0.a
> >
> > make: *** [blib/arch/auto/Compress/Zlib/Zlib.dll] Error 1
> >
> > The output of perl -V is:
{snip - not relevant (but if you don't know, always good to be thorough I
suppose)}
Your attachment shows that you have C: mounted to /c/ as text. It should
be binary (no CR/LF <-> LF conversions). Any drive on which you are
using cc tools (as for instance) should be mounted as binary, I think.
That might not your only problem tho. Do you have unambiguous setup of
your temp dir in your shell environment? What does WinNT %TEMP% and
%TMP% and %TMPDIR% all point to? Are they all defined? Are they (any)
different? (Better not be I think). And, what does Cygwin bash (sh) think is
your tmp dir?
Perl had better have the same idea as everyone else about where tmp is
located. You can check with a simple one-liner I suppose:
perl -e 'print $ENV{TEMP},qq(\n),$ENV{TMP},qq(\n),$ENV{tmp},qq(\n),$ENV{TMPDIR},qq(\n);'
(in Cygwin sh, my system responds that all are "G:\tmp").
(note: in NT's CMD.exe or COMMAND.com as opposed to bash, one must
use double quotes instead of single to wrap the perl expression).
HTH,
soren andersen
-
"Everything that I've learned about computers at MIT I have boiled down into three principles:
- Unix: You think it won't work, but if you find the right wizard, he can make it work.
- Macintosh: You think it will work, but it won't.
- PC/Windows: You think it won't work, and it won't."
-- Philip Greenspun
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -