From: Luke <hazelnusse@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, binutils@sourceware.org
Subject: Re: TARGET undefined in bucomm.c
Date: Wed, 08 Jun 2011 08:28:00 -0000 [thread overview]
Message-ID: <BANLkTintMZ6qXHcp8m2O00WLZD9+hVuqkw@mail.gmail.com> (raw)
In-Reply-To: <m3fwnkeomj.fsf@redhat.com>
Yes. In the build folder (next to the source folder) there are these:
$ find build -name "config.h"
./binutils/config.h
./opcodes/config.h
./libiberty/config.h
./intl/config.h
./bfd/config.h
the bucomm.o target is including finding bfg/config.h, instead of
binutils/config.h:
# 1 "../../binutils-2.21/binutils/bucomm.c"
# 1 "/home/luke/repos/summon-arm-toolchain/build/binutils//"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "../../binutils-2.21/binutils/bucomm.c"
# 26 "../../binutils-2.21/binutils/bucomm.c"
# 1 "../../binutils-2.21/binutils/sysdep.h" 1
# 25 "../../binutils-2.21/binutils/sysdep.h"
# 1 "../../binutils-2.21/binutils/../include/alloca-conf.h" 1
# 1 "../bfd/config.h" 1
# 2 "../../binutils-2.21/binutils/../include/alloca-conf.h" 2
I don't know why that is, but I think it must be the reason TARGETS is
undefined.
~Luke
On Wed, Jun 8, 2011 at 1:03 AM, Andreas Schwab <schwab@redhat.com> wrote:
> Luke <hazelnusse@gmail.com> writes:
>
>> I tried three approaches, all which led to the same error:
>
> Do you have any config.h in the source?
>
> Andreas.
>
> --
> Andreas Schwab, schwab@redhat.com
> GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
> "And now for something completely different."
>
--
"Those who would give up essential liberty to purchase a little
temporary safety deserve neither liberty nor safety."
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759
next prev parent reply other threads:[~2011-06-08 8:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 17:46 Luke
2011-06-06 17:58 ` H.J. Lu
2011-06-06 18:19 ` Luke
2011-06-06 19:32 ` Luke
2011-06-06 20:04 ` Ian Lance Taylor
2011-06-07 3:14 ` Luke
2011-06-07 12:11 ` Ian Lance Taylor
2011-06-07 12:24 ` Andreas Schwab
2011-06-07 18:27 ` Luke
2011-06-07 18:58 ` H.J. Lu
2011-06-08 0:41 ` Luke
2011-06-08 8:03 ` Andreas Schwab
2011-06-08 8:28 ` Luke [this message]
2011-06-08 9:20 ` Alan Modra
2011-06-08 10:08 ` Luke
2011-06-08 11:07 ` Andreas Schwab
2011-06-08 16:28 ` Luke
2011-06-08 13:26 ` Ian Lance Taylor
2011-06-08 16:55 ` Luke
2011-06-08 18:02 ` Ian Lance Taylor
2011-06-08 21:59 ` Luke
2011-06-08 8:49 ` Luke
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=BANLkTintMZ6qXHcp8m2O00WLZD9+hVuqkw@mail.gmail.com \
--to=hazelnusse@gmail.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).