From: "Dave Korn" <dave.korn@artimi.com>
To: "'Sveta'" <zhenja@zlo.ee>, <binutils@sources.redhat.com>
Subject: RE: error building binutils on cygwin
Date: Mon, 19 Jun 2006 11:44:00 -0000 [thread overview]
Message-ID: <000e01c6938c$ec0d31b0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <e732bh$v61$1@sea.gmane.org>
On 18 June 2006 09:32, Sveta wrote:
> I have fresh cygwin installation withour any customisations.
>
> I need to build binutils. Tried different versions from 2.16.1 to 2.16.94.
> Always the same problem, which is shown in the log below. Please give me the
> hint - how to solve that.
I don't know, binutils builds fine for me on cygwin, both from tarballs and
from CVS. I suspect you're having a problem with the crosstool script; you
should try reporting this on the crossgcc list rather than the main binutils
list, because that's where all the crosstools experts hang out.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-06-19 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 10:41 Sveta
2006-06-19 11:44 ` Dave Korn [this message]
2006-06-22 14:11 ` Nick Clifton
2006-06-26 2:52 ` Sveta
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='000e01c6938c$ec0d31b0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=binutils@sources.redhat.com \
--cc=zhenja@zlo.ee \
/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).