* Using g++ and -m32 option on x86_64 broken
@ 2015-07-01 1:39 Jeffrey Walton
2015-07-01 8:29 ` Corinna Vinschen
0 siblings, 1 reply; 4+ messages in thread
From: Jeffrey Walton @ 2015-07-01 1:39 UTC (permalink / raw)
To: cygwin-patches
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...
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using g++ and -m32 option on x86_64 broken 2015-07-01 1:39 Using g++ and -m32 option on x86_64 broken Jeffrey Walton @ 2015-07-01 8:29 ` Corinna Vinschen 2015-07-01 10:59 ` Jeffrey Walton 0 siblings, 1 reply; 4+ messages in thread From: Corinna Vinschen @ 2015-07-01 8:29 UTC (permalink / raw) To: cygwin-patches; +Cc: Jeffrey Walton [-- Attachment #1: Type: text/plain, Size: 2637 bytes --] 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 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/ > And this project really needs a bug tracker... Since this is a GCC problem, it has: https://gcc.gnu.org/bugzilla/ As for -m32, it's not supported for a reason. The link stage requires to provide the 32 bit libs as part of a 64 bit install. This is done on Linux where the 32 bit stuff is in /usr/lib and the 64 bit stuff in /usr/lib64, but we don't do that. Both installations, 32 and 64 bit, use /usr/lib. What we do have is support for cross-compiling using a cross compiler like i686-pc-cygwin-gcc on 64 bit Cygwin and x86_64-pc-cygwin on 32 bit Cygwin. See the cross build packages who's names start with "cygwin32-" on 64 bit, "cygwin64-" on 32 bit. This supported is limited though, because it only provides a limited set of cross libs to link against. It was mainly an effort to support our package maintainers when we introduced 64 bit Cygwin. If you need access to all 32 bit libs, build on 32 bit Cygwin. If you need access to all 64 bit libs, build on 64 bit Cygwin. Alternatively we wouldn't be unhappy for a volunteer (especially given how few volunteers we are) to provide more cross build packages to support easy cross compiling on both platforms. Having a working -m32 utilizing the cross build package path would be the icing on the cake. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using g++ and -m32 option on x86_64 broken 2015-07-01 8:29 ` Corinna Vinschen @ 2015-07-01 10:59 ` Jeffrey Walton 2015-07-01 12:27 ` Corinna Vinschen 0 siblings, 1 reply; 4+ messages in thread From: Jeffrey Walton @ 2015-07-01 10:59 UTC (permalink / raw) To: cygwin-patches 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using g++ and -m32 option on x86_64 broken 2015-07-01 10:59 ` Jeffrey Walton @ 2015-07-01 12:27 ` Corinna Vinschen 0 siblings, 0 replies; 4+ messages in thread From: Corinna Vinschen @ 2015-07-01 12:27 UTC (permalink / raw) To: cygwin-patches; +Cc: Jeffrey Walton [-- Attachment #1: Type: text/plain, Size: 2798 bytes --] On Jul 1 06:59, Jeffrey Walton wrote: > 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. Again, cygwin-patches is for patches to the cygwin DLL, not for GCC patches. I'm politely telling you that you're sending your report to the wrong address so please send you request where it belongs. > > 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. Even then, this doesnt make it an issue for the cygwin-patches ML. > >> 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. You seem to misunderstand how this works. The package maintainers of the various Cygwin packages are not subscribed to cygwin-patches. This mailing list servers only the purpose to send patches for the Cygwin DLL and accompanying tools, as outlined on https://cygwin.com/lists.html. So, if you want to reach out to the Cygwin GCC maintainer, please send your request to the cygwin AT cygwin DOT com mailing list, as outlined on https://cygwin.com/lists.html. Insisting on using the wrong mailing list will not really help to move your complaint forward in the long run. So, please don't follow up on cygwin-patches, it's the wrong addressee. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-07-01 12:27 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-07-01 1:39 Using g++ and -m32 option on x86_64 broken Jeffrey Walton 2015-07-01 8:29 ` Corinna Vinschen 2015-07-01 10:59 ` Jeffrey Walton 2015-07-01 12:27 ` Corinna Vinschen
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).