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:46:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.43.0402161944120.19250-100000@thinkpad.wg-ro-gar1.inext.cz> (raw)
In-Reply-To: <20040216184207.GA26721@nevyn.them.org>
On Mon, 16 Feb 2004, Daniel Jacobowitz wrote:
> > > 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?
No, it's not defined there:
thinkpad:/mnt/karel/gcc340-sim/combined$ grep "AT_SEC" include/elf/common.h
thinkpad:/mnt/karel/gcc340-sim/combined$
Do you think it's worth the test to freshly checkout whole tree again?
Before build I have just rm -rf combined and updated gcc and src
directories, src by: cvs -q up -Pd binutils newlib gdb dejagnu -- do you
think that's the reason for failure?
Thanks,
Karel
--
Karel Gardas kgardas@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
next prev parent reply other threads:[~2004-02-16 18:46 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
2004-02-16 18:46 ` Karel Gardas [this message]
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.0402161944120.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