From: "Cédric Bouttes" <bouttes@ensam.inra.fr>
To: cygwin@cygwin.com
Subject: Compilation problem
Date: Mon, 03 Nov 2003 10:50:00 -0000 [thread overview]
Message-ID: <3.0.1.32.20031103115038.00f86818@ensam.inra.fr> (raw)
Hello,
I'm trying to install DBD-Pg-1.22 on CygWin. I have postgresql and DBI up
and running but i can't get DBD-Pg-1.22 working.
I receive the following error executing make:
$ make
rm -f blib/arch/auto/DBD/Pg/Pg.dll
LD_RUN_PATH="" ld2 -s -L/usr/local/lib Pg.o dbdimp.o -o
blib/arch/auto/DBD/Pg/
Pg.dll /usr/lib/perl5/5.8.0/cygwin-multi-64int/CORE/libperl.dll.a
-L/usr/lib -l
pq
gcc -shared -o Pg.dll -Wl,--out-implib=libPg.dll.a
-Wl,--export-all-symbols -Wl
,--enable-auto-import -Wl,--stack,8388608 \
-s -L/usr/local/lib Pg.o dbdimp.o
/usr/lib/perl5/5.8.0/cygwin-multi-64int/CORE/
libperl.dll.a -L/usr/lib -lpq
dbdimp.o(.text+0x2fde):dbdimp.c: variable '__ctype_' can't be
auto-imported. Ple
ase read the documentation for ld's --enable-auto-import for details.
dbdimp.o(.text+0x2fee):dbdimp.c: variable '__ctype_' can't be
auto-imported. Ple
ase read the documentation for ld's --enable-auto-import for details.
dbdimp.o(.text+0x2ffe):dbdimp.c: variable '__ctype_' can't be
auto-imported. Ple
ase read the documentation for ld's --enable-auto-import for details.
Creating library file: libPg.dll.a
collect2: ld returned 1 exit status
perlld: *** system() failed to execute
gcc -shared -o Pg.dll -Wl,--out-implib=libPg.dll.a
-Wl,--export-all-symbols -Wl
,--enable-auto-import -Wl,--stack,8388608 \
-s -L/usr/local/lib Pg.o dbdimp.o
/usr/lib/perl5/5.8.0/cygwin-multi-64int/CORE/
libperl.dll.a -L/usr/lib -lpq
make: *** [blib/arch/auto/DBD/Pg/Pg.dll] Error 1
What can the problem be???
Regards,
Cédric.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2003-11-03 10:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 10:50 Cédric Bouttes [this message]
2003-11-05 11:46 ` Postgresql: libpq problem? (was: Re: Compilation problem) Gerrit P. Haase
2003-11-05 14:55 ` Jason Tishler
-- strict thread matches above, loose matches on Subject: below --
2020-04-06 9:26 Compilation problem Souleymane SOW
2020-04-06 9:27 ` cygwinautoreply
2007-02-25 21:14 gcc doesn't like my .o file at the end Larry Hall (Cygwin)
2007-02-26 6:19 ` compilation problem nordine
2007-02-26 13:06 ` Larry Hall (Cygwin)
2002-07-17 21:30 Compilation problem Ced
2002-07-18 4:11 ` David Starks-Browning
2002-07-18 6:47 ` Ced
2002-07-18 7:34 ` David Starks-Browning
2002-07-18 7:11 ` Ced
2000-07-19 12:04 compilation problem Earnie Boyd
2000-07-19 7:50 ISNARD Olivier 132311
2000-07-19 8:11 ` Tim Prince
1999-10-14 8:58 Charles McKnight
1999-10-14 22:37 ` Ajit George
1999-10-31 19:54 ` Ajit George
1999-10-31 19:54 ` Charles McKnight
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.1.32.20031103115038.00f86818@ensam.inra.fr \
--to=bouttes@ensam.inra.fr \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).