From: Daniel Jacobowitz <drow@false.org>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb head fails to compile for arm-elf target.
Date: Mon, 16 Feb 2004 18:42:00 -0000 [thread overview]
Message-ID: <20040216184207.GA26721@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.43.0402161937350.19250-100000@thinkpad.wg-ro-gar1.inext.cz>
On Mon, Feb 16, 2004 at 07:38:57PM +0100, Karel Gardas wrote:
> On Mon, 16 Feb 2004, Daniel Jacobowitz wrote:
>
> > On Mon, Feb 16, 2004 at 07:27:39PM +0100, Karel Gardas wrote:
> > >
> > > Hello,
> > >
> > > following information on http://gcc.gnu.org/simtest-howto.html I'm trying
> > > to build gcc and associated gnu tools includig gdb for arm-elf target. The
> > > build fails while compiling gdb with:
> >
> > How have you combined your sources? I'm betting incorrectly.
>
> Yes, I have.
>
> > > ../../combined/gdb/auxv.c: In function `fprint_target_auxv':
> > > ../../combined/gdb/auxv.c:230: error: `AT_SECURE' undeclared (first use in
> > > this function)
> >
> > Please check include/elf/common.h.
>
> thinkpad:/mnt/karel/gcc340-sim/combined$ ls -la include/elf/common.h
> -rw-rw-r-- 2 karel karel 27702 Jan 19 19:28 include/elf/common.h
> thinkpad:/mnt/karel/gcc340-sim/combined$
>
> Sorry, I don't understand, what's wrong with this file?
That should be providing the definition of AT_SECURE. Does it?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-16 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 18:27 Karel Gardas
2004-02-16 18:34 ` Daniel Jacobowitz
2004-02-16 18:39 ` Karel Gardas
2004-02-16 18:42 ` Daniel Jacobowitz [this message]
2004-02-16 18:46 ` Karel Gardas
2004-02-16 18:50 ` Daniel Jacobowitz
2004-02-16 19:54 ` Karel Gardas
2004-02-16 20:42 ` Daniel Jacobowitz
2004-02-16 20:53 ` Karel Gardas
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=20040216184207.GA26721@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kgardas@objectsecurity.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