From: thoni56 <thomas@junovagen.se>
To: cygwin@cygwin.com
Subject: Re: mingw32-gcc and posix paths
Date: Wed, 29 Aug 2012 18:02:00 -0000 [thread overview]
Message-ID: <1346256499860-92389.post@n5.nabble.com> (raw)
In-Reply-To: <503DC812.5060704@users.sourceforge.net>
JonY-6 wrote
>
> On 8/29/2012 14:15, thoni56 wrote:
>>
>> thoni56 wrote
>>>
>>> I'm in the process of going from gcc3 to gcc4. For one project I need to
>>> build both cygwin and win32 executables so "-mno-cygwin" to
>>> "mingw32-gcc"
>>> was an initial hurdle.
>>>
>>> However that is now sorted out, but one thing puzzles me. If the mingw32
>>> is a cygwin cross-compiler why does it not accept paths in the host
>>> format
>>> (meaning cygwin, posix)? To me this seems very natural. Maybe I'm
>>> biased,
>>> but I see no other tools do that, expecting the command line to have the
>>> format of the *target*.
>>>
>>> mingw32-gcc also produces .d files in its native format by the way.
>>>
>>
>> I forgot to add that it is really this .d thing that makes it
>> problematic.
>> The makefiles generate separate subdirectories for various targets and
>> also
>> sets CFLAGS, CC, LINK et al. differently to allow different settings (and
>> compilers, was my theory) for the different targets.
>>
>> Since mingw32-gcc and gcc generates .d files in incompatible formats (gcc
>> really doesn't like "c:\..." in its .d files...) and those are included
>> in
>> the make file, even using different make:s does not solve the problem for
>> me.
>>
>> Any ideas?
>
> Cygwin does not and never has provided a "mingw32-gcc", but it has a
> "i686-pc-mingw32-gcc", it is likely you used those from mingw.org.
>
> mingw.org provides native toolchains, so it is not Cygwin aware, it
> would explain your path issues.
>
Ooops. I was misled by a comment to
http://stackoverflow.com/questions/3776098/cygwin-how-to-actually-use-gcc-mingw
this question on Stackoverflow . As it happened I had a very old version of
mingw32-gcc installed and in my PATH. Sorry about that!
"i686-w64-mingw32-gcc" (which it is in my cygwin) works perfectly. Thanks!
--
View this message in context: http://cygwin.1069669.n5.nabble.com/mingw32-gcc-and-posix-paths-tp92376p92389.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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:[~2012-08-29 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 7:40 thoni56
2012-08-29 7:43 ` thoni56
2012-08-29 15:04 ` JonY
2012-08-29 18:02 ` thoni56 [this message]
2012-08-30 16:45 ` Sven Köhler
2012-08-30 19:22 ` Earnie Boyd
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=1346256499860-92389.post@n5.nabble.com \
--to=thomas@junovagen.se \
--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).