This is the mail archive of the cygwin-patches mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Using g++ and -m32 option on x86_64 broken


On Wed, Jul 1, 2015 at 4:29 AM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> Hi Jeffrey,
>
> On Jun 30 21:38, Jeffrey Walton wrote:
>> 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
>>
>> ************
>
> Wrong mailing list.  cygwin-patches is for patches to the Cygwin
> sources, not patches to arbitrary packages in the Cygwin distro.
> See https://cygwin.com/lists.html

Yes, you got a patch.

> If you want to reach out to Cygwin package maintainers [GCC maintainer
> BCCed], use the cygwin AT cygwin DOT com mailing list.  If you want to
> report the bug to the GCC folks, see https://gcc.gnu.org/bugs/

No, I used Cygwin's package, and that makes it Cygwin's problem.

>> And this project really needs a bug tracker...
>
> As for -m32, it's not supported for a reason.

No, GCC responds to it. If you don't support it, then take it out and
produce a compile error.

Jeff


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]