public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: João Cadamuro Junior <cadamuro@lit.cpdtt.cefetpr.br>
Cc: gdb@sourceware.cygnus.com
Subject: Re: "Tix" failure building Insight-5.0
Date: Fri, 14 Jul 2000 15:04:00 -0000	[thread overview]
Message-ID: <396F8E66.CD618C27@cygnus.com> (raw)
In-Reply-To: <396F8C83.711F668F@lit.cpdtt.cefetpr.br>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]

Jonathan Larmour has a workaround for this problem.
Please try his recipe:

>$ cd /tmp/build/gdb
>$ mv tix/win/tcl8.0/tix4180.dll tix/win/tcl8.0/tix4180.dll.old
>$ cd gdb
>$ make all
>$ cd ..
>$ make -w all install
>



João Cadamuro Junior wrote:
> 
> Hi gdb,
> 
> I have a problem building Insight-5.0 under cygwin 1.1.2 and I don't
> know where to get help: gdb list, insight list or cygwin list. Then,
> I'll try here and, if this is the wrong place, please let me know.
> 
> First, the Insight-5.0 was configured with the options:
> --target=powerpc-eabi --prefix=/tools
> 
> My OS is Windows NT Server 4.0 (SP6).
> 
> At the time of building gdb.exe, the compiler is unable to find the
> funcion Tix_Init. I search for this function and it was found in
> "tix4180.dll", built some minutes before "gdb.exe" in the "make"
> process. Unfortunately, seems that "libtix4180.a" don't have the correct
> information about how to find the funcion Tix_Init in the dll. The
> output of the "make" process was:
> 
> gcc -g -O2       -Wl,--subsystem,console -o gdb.exe main.o libgdb.a
> ../sim/ppc/libsim.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/build/gdb/tk/win -ltk80
> -L/tmp/build/gdb/tcl/win -ltcl80
> -lm -lm
> ../libiberty/libiberty.a -luser32 -lshell32 -lgdi32 -lcomdlg32
> -ladvapi32
> 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'
> 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'
> 
> Someone has an idea about how to solve the problem???
> 
> Thanks in advance...
> 
> Cadamuro

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299

  reply	other threads:[~2000-07-14 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14 14:52 João Cadamuro Junior
2000-07-14 15:04 ` Fernando Nasser [this message]
2000-07-14 15:07   ` Chris Faylor
2000-07-14 15:13     ` Fernando Nasser

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=396F8E66.CD618C27@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=cadamuro@lit.cpdtt.cefetpr.br \
    --cc=gdb@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).