From: JonY <jon_y@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: 64-bit mingw compiler doesn't
Date: Tue, 08 Feb 2011 13:10:00 -0000 [thread overview]
Message-ID: <4D513C14.9050703@users.sourceforge.net> (raw)
In-Reply-To: <4D5125CE.9050406@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/8/2011 19:15, JonY wrote:
> On 2/8/2011 19:14, Csaba Raduly wrote:
>> On Tue, Feb 8, 2011 at 2:51 AM, JonY wrote:
>>>
>>> How did you install mingw64-x86_64? I am puzzled how this can happen,
>>> looks like binutils wasn't installed properly.
>
>> mingw64-x86_64-binutils is a separate package which also has to be
>> selected for installation. mingw64-x86_64-gcc has no dependency on
>> mingw64-x86_64-binutils.
>
>> Csaba
>
> I see this is a packaging problem, odd that it managed to make it pass
> inspection. I will fix this in the next GCC release.
Csaba:
After double checking, I see mingw64-x86_64-binutils as a requirement of
mingw64-x86_64-gcc-core. This should install binutils when you install
mingw-w64 gcc. Can you confirm that its not installed at all?
Daniel:
Can you check if you have mingw64-x86_64-binutils installed?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (MingW32)
iEYEARECAAYFAk1RPAkACgkQp56AKe10wHd1hgCfSjdUGHFEt8eloEwbkSiDCmFD
aAIAn0F7SXtLGnV7omdBX6XHke7gcSin
=jFbS
-----END PGP SIGNATURE-----
[-- Attachment #2: 0xED74C077.asc --]
[-- Type: application/pgp-keys, Size: 1686 bytes --]
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-02-08 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 22:40 Daniel Colascione
2011-02-08 1:51 ` JonY
2011-02-08 10:52 ` Daniel Colascione
2011-02-08 11:14 ` Csaba Raduly
2011-02-08 11:35 ` JonY
2011-02-08 13:10 ` JonY [this message]
2011-02-08 13:33 ` Csaba Raduly
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=4D513C14.9050703@users.sourceforge.net \
--to=jon_y@users.sourceforge.net \
--cc=cygwin@cygwin.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).