From: "Dave Korn" <dave.korn@artimi.com>
To: "'Andrija Radicevic'" <andrija.radicevic@zg.t-com.hr>,
<binutils@sources.redhat.com>
Subject: RE: ld fails to build for target
Date: Tue, 25 Apr 2006 15:21:00 -0000 [thread overview]
Message-ID: <045b01c667db$54c4a4f0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <001601c667d6$8ed6ec70$0a01a8c0@harlequin>
On 24 April 2006 20:38, Andrija Radicevic wrote:
> the thing is that I have the line
>
> e1-*-coff) targ_emul=coff_e1 ;;
>
> in this block, but the case somehow doesn't evaluate the alias e1-coff to
> e1-*-coff
Count the dashes! :)
cheers,
DaveK
--
Can't think of a witty .sigline today....
prev parent reply other threads:[~2006-04-24 20:12 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
2006-04-25 15:21 ` Dave Korn [this message]
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='045b01c667db$54c4a4f0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=andrija.radicevic@zg.t-com.hr \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).