From: "Gerrit van Niekerk" <gerritvn@gpvno.co.za>
To: gdb@sourceware.org
Subject: Re: Problem building cross-debugger
Date: Fri, 18 Jan 2008 16:26:00 -0000 [thread overview]
Message-ID: <4790EF3A.8104.1D28BDA@gerritvn.gpvno.co.za> (raw)
In-Reply-To: <47908F14.31772.5AD24E@gerritvn.gpvno.co.za>
>> I am trying to use Cygwin to build a Cygwin host, DJGPP target version of GDB:
>> config --target=djgpp All libraries seem to build ok (make does not stop), but
>> the final link gives a number of undefined references
> There is now only one undefined reference remaining: `_bfd_i386_arch'
This is turning out to be a very one-sided thread :)
I managed to get the link phase to work by explicitly including ../bfd/cpu-i386.o in the gcc
command doing the final link. Perhaps the GDB maintainers can have a look at the cause of the
problem.
BTW: The resulting cross-gdb is working like a charm :)
next prev parent reply other threads:[~2008-01-18 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 22:20 Gerrit van Niekerk
2008-01-18 9:36 ` Gerrit van Niekerk
2008-01-18 16:26 ` Gerrit van Niekerk [this message]
2008-01-18 18:53 ` Jim Blandy
2008-01-18 19:27 ` Gerrit van Niekerk
2008-02-11 20:02 ` Michael Shatz
2008-02-13 17:49 ` Michael Shatz
2008-02-13 20:21 ` Gerrit van Niekerk
2008-02-13 21:19 ` Brian Dessent
2008-02-13 20:49 ` Dave Korn
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=4790EF3A.8104.1D28BDA@gerritvn.gpvno.co.za \
--to=gerritvn@gpvno.co.za \
--cc=gdb@sourceware.org \
--cc=gpvno@telkomsa.net \
/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