* Re: Updated: mingw-runtime-3.18-3 [not found] <201106020502.p5252MaN022999@alum-mailsec-relay-3.mit.edu> @ 2011-06-03 21:38 ` Jim Reisert AD1C 2011-06-03 22:11 ` René Berber 2011-06-04 17:50 ` Jim Reisert AD1C 0 siblings, 2 replies; 6+ messages in thread From: Jim Reisert AD1C @ 2011-06-03 21:38 UTC (permalink / raw) To: The Cygwin Mailing List What is the easiest way to transition from the gcc3 environment? gcc -mno-cygwin ... to the equivalent compile using gcc4 (I can hand off a .exe file w/o cygwin1.dll)? Thanks - Jim -- Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us -- 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated: mingw-runtime-3.18-3 2011-06-03 21:38 ` Updated: mingw-runtime-3.18-3 Jim Reisert AD1C @ 2011-06-03 22:11 ` René Berber 2011-06-04 1:01 ` JonY 2011-06-04 17:50 ` Jim Reisert AD1C 1 sibling, 1 reply; 6+ messages in thread From: René Berber @ 2011-06-03 22:11 UTC (permalink / raw) To: cygwin On 6/3/2011 4:38 PM, Jim Reisert AD1C wrote: > What is the easiest way to transition from the gcc3 environment? > > gcc -mno-cygwin ... > > to the equivalent compile using gcc4 (I can hand off a .exe file w/o > cygwin1.dll)? Use i686-pc-mingw32-gcc instead. -- René Berber -- 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated: mingw-runtime-3.18-3 2011-06-03 22:11 ` René Berber @ 2011-06-04 1:01 ` JonY 0 siblings, 0 replies; 6+ messages in thread From: JonY @ 2011-06-04 1:01 UTC (permalink / raw) To: cygwin [-- Attachment #1.1: Type: text/plain, Size: 410 bytes --] On 6/4/2011 06:10, René Berber wrote: > On 6/3/2011 4:38 PM, Jim Reisert AD1C wrote: >> What is the easiest way to transition from the gcc3 environment? >> >> gcc -mno-cygwin ... >> >> to the equivalent compile using gcc4 (I can hand off a .exe file w/o >> cygwin1.dll)? > > Use i686-pc-mingw32-gcc instead. or --host=i686-pc-mingw32 --build=i686-pc-cygwin for autotools based build systems. [-- Attachment #1.2: 0xED74C077.asc --] [-- Type: application/pgp-keys, Size: 1715 bytes --] [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 196 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated: mingw-runtime-3.18-3 2011-06-03 21:38 ` Updated: mingw-runtime-3.18-3 Jim Reisert AD1C 2011-06-03 22:11 ` René Berber @ 2011-06-04 17:50 ` Jim Reisert AD1C 2011-06-04 18:22 ` René Berber 1 sibling, 1 reply; 6+ messages in thread From: Jim Reisert AD1C @ 2011-06-04 17:50 UTC (permalink / raw) To: The Cygwin Mailing List On Fri, Jun 3, 2011 at 3:38 PM, I asked: > What is the easiest way to transition from the gcc3 environment? > > gcc -mno-cygwin ... > > to the equivalent compile using gcc4 (I can hand off a .exe file w/o > cygwin1.dll)? René Berber suggested: > Use i686-pc-mingw32-gcc instead. That worked, thanks. That's not 100% correct, though, the command is (or seems to be): i686-w64-mingw32-gcc -- Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us -- 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated: mingw-runtime-3.18-3 2011-06-04 17:50 ` Jim Reisert AD1C @ 2011-06-04 18:22 ` René Berber 2011-06-04 18:40 ` Charles Wilson 0 siblings, 1 reply; 6+ messages in thread From: René Berber @ 2011-06-04 18:22 UTC (permalink / raw) To: cygwin On 6/4/2011 12:49 PM, Jim Reisert AD1C wrote: > René Berber suggested: > >> Use i686-pc-mingw32-gcc instead. > > That worked, thanks. That's not 100% correct, though, the command is > (or seems to be): > > i686-w64-mingw32-gcc One is for 32-bit the other for 64-bit, but the 64-bit is supposed to be capable of producing both kind of binaries, I don't use it so I'm not sure if they reached that objective. -- René Berber -- 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated: mingw-runtime-3.18-3 2011-06-04 18:22 ` René Berber @ 2011-06-04 18:40 ` Charles Wilson 0 siblings, 0 replies; 6+ messages in thread From: Charles Wilson @ 2011-06-04 18:40 UTC (permalink / raw) To: cygwin On 6/4/2011 2:22 PM, René Berber wrote: > On 6/4/2011 12:49 PM, Jim Reisert AD1C wrote: >> René Berber suggested: >> >>> Use i686-pc-mingw32-gcc instead. >> >> That worked, thanks. That's not 100% correct, though, the command is >> (or seems to be): >> >> i686-w64-mingw32-gcc No, the mingw-gcc(-core) package provides i686-pc-mingw32-gcc.exe. The mingw64-i686-gcc(-core) package provides i686-w64-mingw32-gcc.exe. The difference between the two is: 1) mingw-gcc (that is, i686-pc-mingw32-*) is based on the mingw.org distribution. It uses the mingw-runtime (e.g. msvcrt implibs & headers) and w32api headers developed by that project -- which happen to be the same as the ones used by the cygwin project itself. 2) mingw64-i686-gcc (that is, i686-w64-mingw32-*) is based on the mingw64.sf.net distribution. It uses a different, and independently developed, version of the msvcrt implibs, headers, and w32api headers. It shares this distinction with the mingw64-x86_64-gcc (that is, x86_64-w64-mingw32-*) compiler. However, the i686-w64 version creates 32bit output -- ONLY. the x86_64-w64 version creates 64bit output ONLY. Furthermore, both the i686-w64 and x86_64-w64 versions use "sjlj" exception handling, while the i686-pc version uses "dw2" exception handling. > One is for 32-bit the other for 64-bit, but the 64-bit is supposed to be > capable of producing both kind of binaries, I don't use it so I'm not > sure if they reached that objective. This is completely wrong. -- Chuck -- 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-06-04 18:40 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <201106020502.p5252MaN022999@alum-mailsec-relay-3.mit.edu> 2011-06-03 21:38 ` Updated: mingw-runtime-3.18-3 Jim Reisert AD1C 2011-06-03 22:11 ` René Berber 2011-06-04 1:01 ` JonY 2011-06-04 17:50 ` Jim Reisert AD1C 2011-06-04 18:22 ` René Berber 2011-06-04 18:40 ` Charles Wilson
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).