From: Nick Clifton <nickc@redhat.com>
To: Andrija Radicevic <andrija.radicevic@zg.t-com.hr>
Cc: Andreas Schwab <schwab@suse.de>, Dave Korn <dave.korn@artimi.com>,
binutils@sources.redhat.com
Subject: Re: ld fails to build for target
Date: Tue, 25 Apr 2006 17:12:00 -0000 [thread overview]
Message-ID: <444E5030.4020905@redhat.com> (raw)
In-Reply-To: <000d01c66882$f5df09f0$0a01a8c0@harlequin>
Hi Andrija,
>> Lets have a look at these ld/configure.tgt and config.sub files of
>> yours. Can you tar them up, zip them up and then post them ?
>
> here are the files
Right, so the config.sub file you sent does translate "e1-coff" into
"e1-unknown-coff" and the configure.tgt file does recognise a target of
"e1-unknown-coff".
Since the error message that you get from configure.tgt show that it
does not recognise "e1-coff" it follows that this translation from
"e1-coff" into "e1-unknown-coff" is not being performed. You need to
check what is happening in the ld/configure script around these lines:
# Canonicalize the secondary target names.
result=`$ac_config_sub $targ_alias 2>/dev/null`
if test -n "$result"; then
targ=$result
else
targ=$targ_alias
fi
. ${srcdir}/configure.tgt
This starts at line 9702 in the version of the configure file that I
have here. Presumably the invocation of "result=`$ac_config_sub
$targ_alias`" is not working. You need to find out why.
Cheers
Nick
next prev parent reply other threads:[~2006-04-25 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 18:28 Andrija Radicevic
2006-04-24 19:37 ` Dave Korn
2006-04-25 2:27 ` Andrija Radicevic
2006-04-25 3:22 ` Andreas Schwab
2006-04-25 15:23 ` Andrija Radicevic
2006-04-25 16:40 ` Nick Clifton
2006-04-25 17:09 ` Andrija Radicevic
2006-04-25 17:12 ` Nick Clifton [this message]
2006-04-25 19:56 ` Andrija Radicevic
2006-05-01 15:34 ` Andrija Radicevic
2006-04-25 15:21 ` Dave Korn
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=444E5030.4020905@redhat.com \
--to=nickc@redhat.com \
--cc=andrija.radicevic@zg.t-com.hr \
--cc=binutils@sources.redhat.com \
--cc=dave.korn@artimi.com \
--cc=schwab@suse.de \
/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).