public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Alberto Stapelfeld <astapelfeld@ieee.org>
Cc: insight@sourceware.cygnus.com
Subject: Re: Problems when building Insight
Date: Tue, 25 Apr 2000 04:46:00 -0000	[thread overview]
Message-ID: <20000425074608.C9380@cygnus.com> (raw)
In-Reply-To: <005c01bfae80$f98ae6e0$3c2830c8@homepc>

You are building using a cygwin snapshot but you probably haven't installed
everything in a consistent location.

This error shows up very very very very very very very very frequently
when people download a cygwin snapshot but do not have all of the
libraries in a consistent place on their system.

I would suggest either 1) downloading the newest cygwin net release and
building everything with that, 2) perusing the cygwin mailing list archives
(reachable via http://sourceware.cygnus.com/cygwin/ ), or 3) sending a message
to the cygwin mailing list: cygwin@sourceware.cygnus.com.

On Tue, Apr 25, 2000 at 01:39:08AM -0500, Alberto Stapelfeld wrote:
>I sent this message to ecos-discuss mailing list, but I've got no response,
>I would appreciate your help.
>
> ----- Original Message -----
> From: "Alberto Stapelfeld" <astapelfeld@ieee.org>
> To: "eCos discuss" <ecos-discuss@sourceware.cygnus.com>
> Sent: Thursday, April 20, 2000 5:14 PM
> Subject: Problems when building Insight
>
>
> > I'm using the following files :
> >
> > binutils-000416.tar
> > gcc-core-2.95.2.tar
> > gcc-g++-2.95.2.tar
> > insight+dejagnu-weekly-20000412.tar
> > full.exe  (Cygwin)
> > cygwin-20000301.tar.gz
> > ecos-net-gcc-2.95.2-patchset
> >
> > Then I followed the instruction of the doc : "Building the Intel x86
> > development tools for Windows", During the step 6 (Build and install
> > Insight), I get these messages :
> >
> > ....
> > gcc -g -O2       -Wl,--subsystem,console -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`
> >
> >
> >
> >
>
>../libgui/src/libgui.a -L/tmp/build/gdb/itcl/itcl/win -litcl30 -L/tmp/build/
> >
>
>gdb/itcl/itk/win -litk30 -L/tmp/build/gdb/tix/win/tcl8.0 -ltix4180 -L/tmp/bu
> > ild/gdb/tk/win -ltk80 -L/tmp/build/gdb/tcl/win -ltcl80      -lm -lm
> > ../libiberty/libiberty.a -luser32 -lshell32 -lgdi32 -lcomdlg32 -ladvapi32
> >
>
>g:\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_'
> >
>g:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\../
>> libtermcap.a(termcap.o): In function `tgetent':
> > /home/noer/src/b20/comp-tools/devo/libtermcap/termcap.c:251: undefined
> > reference to `_ctype_'
> >
>
>g:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\../
> > libtermcap.a(getcap.o): In function `cgetnext':
> > /home/noer/src/b20/comp-tools/devo/libtermcap/getcap.c:686: undefined
> > reference to `_ctype_'
> > collect2: ld returned 1 exit status
> > make[1]: *** [gdb.exe] Error 1
> > make[1]: Leaving directory `/tmp/build/gdb/gdb'
> > make: *** [all-gdb] Error 2
> > make: Leaving directory `/tmp/build/gdb'
> >
> > What's wrong?
> >
> >
> > Alberto Stapelfeld.

-- 
cgf@cygnus.com                        Cygnus Solutions, a Red Hat company
http://sourcware.cygnus.com/          http://www.redhat.com/

      reply	other threads:[~2000-04-25  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-24 23:41 Alberto Stapelfeld
2000-04-25  4:46 ` Chris Faylor [this message]

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=20000425074608.C9380@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=astapelfeld@ieee.org \
    --cc=insight@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).