public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andreas.Karlsson@combitechsystems.com
To: jlarmour@redhat.co.uk
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Error while making insight-5.0
Date: Mon, 03 Jul 2000 04:42:00 -0000	[thread overview]
Message-ID: <2253171AF143D21185A60000F8FA748B01F97E6A@pluto.combitech.se> (raw)

The output from nm follows:

bash-2.04$ nm libtix4180.a | grep Tix_Init
00000000 T _Tix_InitScrollInfo
00000000 I __imp__Tix_InitScrollInfo
00000000 T _Tix_Init
00000000 I __imp__Tix_Init
bash-2.04$

-----Original Message-----
From: Jonathan Larmour [ mailto:jlarmour@redhat.co.uk ]
Sent: den 3 juli 2000 13:21
To: Karlsson Andreas
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Error while making insight-5.0


Andreas.Karlsson@combitechsystems.com wrote:
> libgdb.a(gdbtk.o): In function `gdbtk_init':
> /src/gdb/insight-5.0/gdb/gdbtk/generic/gdbtk.c:433: undefined reference to
> `Tix_Init'
> /src/gdb/insight-5.0/gdb/gdbtk/generic/gdbtk.c:435: undefined reference to
> `Tix_Init'

Is there a file tix/win/tcl8.0/libtix4.1.8.0.a in your build tree? If so,
run the command:

nm tix/win/tcl8.0/libtix4.1.8.0.a | grep Tix_Init

Does that indicate the symbol is there?

If not, go into the tix subdirectory and type "make clean". Then go back up
and rerun the "make -w all ...."

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

             reply	other threads:[~2000-07-03  4:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-03  4:42 Andreas.Karlsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-03  7:02 Andreas.Karlsson
2000-07-03  3:53 Andreas.Karlsson
2000-07-03  4:21 ` Jonathan Larmour

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=2253171AF143D21185A60000F8FA748B01F97E6A@pluto.combitech.se \
    --to=andreas.karlsson@combitechsystems.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.co.uk \
    /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).