public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Iain Wiseman <iwiseman@g8labs.co.nz>
Cc: Insight <insight@sourceware.cygnus.com>
Subject: Re: libtermcap linking
Date: Thu, 13 Apr 2000 19:49:00 -0000	[thread overview]
Message-ID: <20000413224857.B16027@cygnus.com> (raw)
In-Reply-To: <KNEFKNCDGHCJGDAOBJEKGEDACBAA.iwiseman@g8labs.co.nz>

If you are using cygwin snapshots then you have to be aware of how to
use them.  The snapshots are not intended for casual compilers.

Please check the cygwin mailing list archives for details on
what you are doing wrong.  This issue has been rehashed constantly
there.

cgf

On Fri, Apr 14, 2000 at 12:17:42PM +1200, Iain Wiseman wrote:
>I am trying to build gdb and receive the following errors. I am using B20.1
>with cygwin-inst-20000410.tar.gz installed over the top. ie.
>
>insight+dejagnu-weekly-20000412.tar
>
>cygwin-inst-20000410.tar.gz
>cygwin1-20000410.dll.gz
>
>gcc -g -O2        -o gdb.exe main.o libgdb.a    ../bfd/libbfd.a
>../readline/libreadline.a ../opcodes/libopcodes.a ./../intl/libintl.a
>../libiberty/libiberty.a `if test -r ../libtermcap/libtermcap.a; then echo
>../libtermcap/libtermcap.a; else echo -ltermcap; fi`     -lm
>../libiberty/libiberty.a -luser32 -limagehlp
>f:\CYGWIN~1\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\
>..\..\../libtermcap.a(tputs.o): In function `tputs':
>/home/noer/src/b20/comp-tools/devo/libtermcap/tputs.c:72: undefined
>reference to `_ctype_'
>/home/noer/src/b20/comp-tools/devo/libtermcap/tputs.c:75: undefined
>reference to `_ctype_'
>/home/noer/src/b20/comp-tools/devo/libtermcap/tputs.c:80: undefined
>reference to `_ctype_'
>f:\CYGWIN~1\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\
>..\..\../libtermcap.a(te
>rmcap.o): In function `tgetent':
>/home/noer/src/b20/comp-tools/devo/libtermcap/termcap.c:251: undefined
>reference to `_ctype_'
>f:\CYGWIN~1\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\
>..\..\../libtermcap.a(ge
>tcap.o): In function `cgetnext':
>/home/noer/src/b20/comp-tools/devo/libtermcap/getcap.c:686: undefined
>reference to `_ctype_'
>
>Many thanks in advance
>------------------------------------------------------------
>Is your argument so weak that it cannot stand debate - Data
>
>"Most Toys -STNG"
>
> mailto:bibble@ibm.net
>

  reply	other threads:[~2000-04-13 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-13 17:18 Iain Wiseman
2000-04-13 19:49 ` Chris Faylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-13 16:24 Iain Wiseman

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=20000413224857.B16027@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=iwiseman@g8labs.co.nz \
    /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).