From: Jeffrey Walton <noloader@gmail.com>
To: cygwin-patches@cygwin.com
Subject: Using g++ and -m32 option on x86_64 broken
Date: Wed, 01 Jul 2015 01:39:00 -0000 [thread overview]
Message-ID: <CAH8yC8mUrhuR2vPhqSSLKmrA82nW3JhvcRnFVO1nFccy337y_g@mail.gmail.com> (raw)
Cygwin's GCC responds to the -m32 option, but it causes a compile error:
expected unqualified-id before ‘__int128’
inline __int128
If the project does not support the -m32 option, then it should be
removes so that using it causes a compile error.
Below is the changed needed to get through the compile with -m32:
$ diff /usr/lib/gcc/x86_64-pc-cygwin/4.9.2/include/c++/x86_64-pc-cygwin/bits/c++config.h
/usr/lib/gcc/x86_64-pc-cygwin/4.9.2/include/c++/x86_64-pc-cygwin/bits/c++config.h.bu
1306,1308c1306
< #ifndef __CYGWIN32__ /* -m32 used on x86_64 */
< # define _GLIBCXX_USE_INT128 1
< #endif
---
> #define _GLIBCXX_USE_INT128 1
************
And this project really needs a bug tracker...
next reply other threads:[~2015-07-01 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 1:39 Jeffrey Walton [this message]
2015-07-01 8:29 ` Corinna Vinschen
2015-07-01 10:59 ` Jeffrey Walton
2015-07-01 12:27 ` Corinna Vinschen
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=CAH8yC8mUrhuR2vPhqSSLKmrA82nW3JhvcRnFVO1nFccy337y_g@mail.gmail.com \
--to=noloader@gmail.com \
--cc=cygwin-patches@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).