From: jtc@redback.com (J.T. Conklin)
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Kevin Buettner <kevinb@cygnus.com>,
GDB Discussion <gdb@sources.redhat.com>
Subject: Re: ia64 target?
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <5msnkdnw9n.fsf@jtc.redback.com> (raw)
In-Reply-To: <3AB296E0.3AF3ADD1@cygnus.com>
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
>> That might be considered an OK limitation for Linux targets. But if
>> we're going to have a config listed in the MAINTAINERS list so we can
>> use it to verify that global changes don't break builds, we have to
>> ensure that those configs build on all hosts.
Andrew> Keven recently fixed this - you really can cross compile shared library
Andrew> support for linux targets (I'm pretty sure I double checked a !linux X
Andrew> ia64-linux before updating this).
Ummm, I wouldn't have sent a message if the ia64-linux target wasn't
failing on my nightly builds (i386-netbsd1.3 host).
--jtc
gcc -c -g -O2 -I. -I../../gdb -I../../gdb/config -DHAVE_CONFIG_H -I../../gdb/../include/opcode -I../../gdb/../readline/.. -I../bfd -I../../gdb/../bfd -I../../gdb/../include -I../intl -I../../gdb/../intl -DUI_OUT=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith ../../gdb/solib-legacy.c
In file included from ../../gdb/solib-legacy.c:28:
/usr/include/link.h:85: field `nlist' has incomplete type
../../gdb/solib-legacy.c: In function `legacy_svr4_fetch_link_map_offsets':
../../gdb/solib-legacy.c:53: sizeof applied to an incomplete type
../../gdb/solib-legacy.c:55: dereferencing pointer to incomplete type
../../gdb/solib-legacy.c:56: dereferencing pointer to incomplete type
../../gdb/solib-legacy.c:58: sizeof applied to an incomplete type
../../gdb/solib-legacy.c:60: dereferencing pointer to incomplete type
../../gdb/solib-legacy.c:61: dereferencing pointer to incomplete type
../../gdb/solib-legacy.c:63: dereferencing pointer to incomplete type
../../gdb/solib-legacy.c:64: dereferencing pointer to incomplete type
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 Andrew Cagney
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` J.T. Conklin [this message]
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin
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=5msnkdnw9n.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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).