Cross-compiling for i686-pc-mingw32

Larry Hall (Cygwin)
Wed Sep 1 15:03:00 GMT 2010

On 9/1/2010 10:35 AM, Andrey Repin wrote:
> Greetings, Charles Wilson!
>>> With cygwin-1.5.25 I can cross-compile libraries for native win32 by
>>> starting with the following configure command:
>>> ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin CC='gcc
>>> -mno-cygwin' host_alias=i686-pc-mingw32
>>> and that has worked fine on the few occasions that I've tried it.
>>> However, with cygwin-1.7.5, it doesn't work.
>> For now, use CC='gcc-3 -mno-cygwin'. Soon you'll be able to use a real,
>> honest-to-god cross compiler version of gcc-4 instead (e.g.
>> "i686-pc-mingw32-gcc")
> Aww... now i'm struck with it.
> Tried to compile
> Installed gcc-mingw, it pulled up some additional packets including gcc
> itself.
> Then I ran make just for test. Cygwin build went fine, apart from htpasswd
> (there's getline redefined in source), but I don't really need it.
> Then tried to switch to mingw32 and...
> $ gcc -b i686-pc-mingw32 -O   -c mini_httpd.c
> gcc: couldn't run `i686-pc-mingw32-gcc-3.4.4': No such file or directory
> Tried the suggested gcc-3 -mno-cygwin, and got a whole bunch of unresolved
> function names.
> So... am I doing something wrong or it's not yet ready to do so?

Can you be more specific about what you did?  For example, your original
post stated you could use 'gcc -mno-cygwin' when configuring back in the
days of 1.5.x.  Are you saying that substituting 'gcc-3' for 'gcc' in that
invocation doesn't work with 1.7.x?  If so, we need to see more details.  See

Problem reports:

Larry Hall                    
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746


A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list