From: jtc@redback.com (J.T. Conklin)
To: Kevin Buettner <kevinb@cygnus.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: ia64 target?
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <5msnk9l5yh.fsf@jtc.redback.com> (raw)
In-Reply-To: <1010319082642.ZM5967@ocotillo.lan>
>>>>> "Kevin" == Kevin Buettner <kevinb@cygnus.com> writes:
>> > Ummm, I wouldn't have sent a message if the ia64-linux target wasn't
>> > failing on my nightly builds (i386-netbsd1.3 host).
>>
>> Puzzled expression :-)
>>
>> Just put it back to broken for now and then Kevin and/or I will figure
>> out what happened.
Kevin> I was able to reproduce J.T.'s problem on NetBSD 1.4 and have
Kevin> fixed it. See
Kevin> http://sources.redhat.com/ml/gdb-patches/2001-03/msg00341.html
Kevin> for the details. (I would appreciate it though if J.T. would
Kevin> retest on his NetBSD 1.3 box.)
It's closer.
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
It appears that 1.3 requires nlist.h to be included before link.h.
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AAEA47E.339FF4BD@cygnus.com>
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin
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 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin [this message]
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 ` Andrew Cagney
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=5msnk9l5yh.fsf@jtc.redback.com \
--to=jtc@redback.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