From: Kevin Buettner <kevinb@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: can't build cross-gdb for --target=mips-sgi-irix6
Date: Tue, 01 Oct 2002 18:08:00 -0000 [thread overview]
Message-ID: <1021002010805.ZM20744@localhost.localdomain> (raw)
In-Reply-To: Alexandre Oliva <aoliva@redhat.com> "can't build cross-gdb for --target=mips-sgi-irix6" (Oct 1, 9:49pm)
On Oct 1, 9:49pm, Alexandre Oliva wrote:
> mips-sgi-irix6-gdb (5.3 branch and mainline) failed to link on
> athlon-pc-linux-gnu. breakpoint.c didn't to compile in
> disable_breakpoints_in_shlibs() because SOLIB_ADD was not defined. I
> think solib.h must be #included somewhere, and I think the right place
> is config/mips/tm-irix6.h. I couldn't test this natively, because I
> don't have access to any irix box at the moment, but the cross
> debugger built correctly with this patch. Ok to install?
Yes.
Normally, we also try to remove the #include of solib.h from the
appropriate nm-*.h files. However, we can't easily do that for
Irix since nm-irix6.h includes nm-irix5.h which includes
config/nm-sysv4.h. This latter file is used by a lot of other
platforms. Once our Irix system is running again, I'll see if
I can figure out what should be done so that solib.h isn't included
more than once. (Including it more than once is safe though because
solib.h protects itself from multiple inclusions.)
Thanks,
Kevin
prev parent reply other threads:[~2002-10-02 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 17:50 Alexandre Oliva
2002-10-01 17:54 ` Daniel Jacobowitz
2002-10-01 17:59 ` Alexandre Oliva
2002-10-01 18:08 ` Kevin Buettner [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=1021002010805.ZM20744@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=aoliva@redhat.com \
--cc=gdb-patches@sources.redhat.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