From: "Andre Oliveira da Costa" <costa@cade.com.br>
To: "Cygwin" <cygwin@sourceware.cygnus.com>
Subject: NcFTP's configure & readline
Date: Fri, 31 Dec 1999 13:28:00 -0000 [thread overview]
Message-ID: <000001bf3d10$732d1a50$8400000a@costa.cadenet.com.br> (raw)
Message-ID: <19991231132800.CmsvXGheudhh6DUHu-rMpwlCswOlOxHiNOUIpfycrnc@z> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Hi,
while trying to compile ncftp v2.4.3 for cygwin B20.1 (patched with 19991122
snapshot), its configure script complained about not being able to find
readline. Since I know libreadline.a lives on /cygnus/.../lib/libreadline.a,
I decided to take a closer look at config.log, and I found this:
configure:2436: gcc -o conftest -O2 -I/usr/local/include -L/usr/local/lib
confte
st.c -lreadline 1>&5
c:\cygnus\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..
\..\
../libreadline.a(readline.o)(.text+0x1815):readline.c: undefined reference
to `_ctype_'
Looking even closer, I realized all the complaints were about the same
_ctype_, which a grep on the include files at /cygnus/.../include reports as
being defined on ctype.h. Is there anything strange with my configuration or
should I have done something else on the configure phase?
My cygwin is B20.1, with cygwin-inst-19991122.tar.gz installed over it. I
attached the output of cygcheck -s in case anybody would like to take a look
at it.
TIA,
Andre
--
André Oliveira da Costa
(costa@cade.com.br)
next reply other threads:[~1999-12-31 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 14:01 Andre Oliveira da Costa [this message]
1999-12-31 13:28 ` Andre Oliveira da Costa
[not found] <3.0.5.32.19991202170913.00e64230@pop.ma.ultranet.com>
1999-12-03 4:58 ` Andre Oliveira da Costa
1999-12-31 13:28 ` Andre Oliveira da Costa
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='000001bf3d10$732d1a50$8400000a@costa.cadenet.com.br' \
--to=costa@cade.com.br \
--cc=cygwin@sourceware.cygnus.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).