public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Andrija Radicevic" <andrija.radicevic@zg.t-com.hr>
To: "Nick Clifton" <nickc@redhat.com>
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: Mon, 01 May 2006 15:34:00 -0000	[thread overview]
Message-ID: <001501c66d34$cabf4ee0$0a01a8c0@harlequin> (raw)
In-Reply-To: <002401c6688f$0b98c090$0a01a8c0@harlequin>

>
>>
>> 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
>>
>
> I have found the part in my configure file, dough it looks a little bit 
> different
>
>    # Canonicalize the secondary target names.
>    result=`${CONFIG_SHELL-/bin/sh} $ac_config_sub $targ_alias 2>/dev/null`
>    if test -n "$result"; then
> targ=$result
>    else
> targ=$targ_alias
>    fi
>
>    . ${srcdir}/configure.tgt
>
> obviously it must end up in the else branch (targ=$targ_alias) as you 
> already said. Now I have to figure out why this happens.
> Thanks for your help.
>

Hi,

It turnd out that
${CONFIG_SHELL-/bin/sh} evaluates to /bin/sh
and
$ac_config_sub to /bin/sh ../../binutils-2.16/ld/../config.sub
which together obiously results with an awkward construct

After I have removed ${CONFIG_SHELL-/bin/sh}  from that particular line in 
the ld/configure script, ld was built. Now, I wonder what went wrong? I 
suspect that the autoconf (2.59) and automake (1.9.2) versions I was using 
messed the thing up. I haven't built those myself, they came with the Fedora 
Core 3 distribution I have installed on my machine.

regards

Andrija 

  reply	other threads:[~2006-05-01 15:34 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
2006-04-25 19:56               ` Andrija Radicevic
2006-05-01 15:34                 ` Andrija Radicevic [this message]
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='001501c66d34$cabf4ee0$0a01a8c0@harlequin' \
    --to=andrija.radicevic@zg.t-com.hr \
    --cc=binutils@sources.redhat.com \
    --cc=dave.korn@artimi.com \
    --cc=nickc@redhat.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).