Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Karel Gardas <kgardas@objectsecurity.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb head fails to compile for arm-elf target.
Date: Mon, 16 Feb 2004 18:39:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.43.0402161937350.19250-100000@thinkpad.wg-ro-gar1.inext.cz> (raw)
In-Reply-To: <20040216183443.GA26490@nevyn.them.org>

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?

Thanks,

Karel
--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com


  reply	other threads:[~2004-02-16 18:39 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 [this message]
2004-02-16 18:42     ` Daniel Jacobowitz
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=Pine.LNX.4.43.0402161937350.19250-100000@thinkpad.wg-ro-gar1.inext.cz \
    --to=kgardas@objectsecurity.com \
    --cc=drow@false.org \
    --cc=gdb@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