From: Mumit Khan <khan@xraylith.wisc.EDU>
To: "Kai-Uwe Rommel" <rommel@ars.de>
Cc: DJ Delorie <dj@delorie.com>, cygwin@sourceware.cygnus.com
Subject: Re: B20.1: how to build for MinGW32?
Date: Sun, 07 Mar 1999 21:30:00 -0000 [thread overview]
Message-ID: <199903080530.XAA21364@modi.xraylith.wisc.edu> (raw)
In-Reply-To: Your message of "Sun, 07 Mar 1999 20:01:13 +0100." < C125672D.00688D51.00@abraham.ars.de >
"Kai-Uwe Rommel" <rommel@ars.de> writes:
>
> DJ Delorie <dj@delorie.com> wrote on 7.3.1999 19:08:28:
> >
> > > Since I can't find notes about that in the docs, here is my
> > > question: what is the official way of recompiling the code for
> > > MinGW32?
> >
> > Mingw doesn't provide a posix emulation, so I wouldn't expect GNU
> > tools to build with it. I think our expectation is that the
> > development tools would always be built with cygwin, and would
> > cross-compile to mingw.
>
> So how do I cross-compile with CygWin to MinGW32? I finally managed
> to get the thing compiled, but after "configure" I had to add
> -mno-cygwin manually to the Makefile's "CC = gcc" statements and
> also had to manually edit some config.h files.
>
> Probably I already have to tell "configure" to use -mno-cygwin, but
> how? I am still not all too familiar with CygWin and configure ...
Have you looked at my howto for building mingw cross compiler? That may
answer your question.
See http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
I've never tried building under cygwin, but in theory it should work just
as well as under Linux or other well supported Unix'y hosts.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: "Kai-Uwe Rommel" <rommel@ars.de>
Cc: DJ Delorie <dj@delorie.com>, cygwin@sourceware.cygnus.com
Subject: Re: B20.1: how to build for MinGW32?
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <199903080530.XAA21364@modi.xraylith.wisc.edu> (raw)
Message-ID: <19990331194500.a0_6PsCDGr4XfGjEODD72BpVguZFdqGdWFBUq_A66X0@z> (raw)
In-Reply-To: <C125672D.00688D51.00@abraham.ars.de>
"Kai-Uwe Rommel" <rommel@ars.de> writes:
>
> DJ Delorie <dj@delorie.com> wrote on 7.3.1999 19:08:28:
> >
> > > Since I can't find notes about that in the docs, here is my
> > > question: what is the official way of recompiling the code for
> > > MinGW32?
> >
> > Mingw doesn't provide a posix emulation, so I wouldn't expect GNU
> > tools to build with it. I think our expectation is that the
> > development tools would always be built with cygwin, and would
> > cross-compile to mingw.
>
> So how do I cross-compile with CygWin to MinGW32? I finally managed
> to get the thing compiled, but after "configure" I had to add
> -mno-cygwin manually to the Makefile's "CC = gcc" statements and
> also had to manually edit some config.h files.
>
> Probably I already have to tell "configure" to use -mno-cygwin, but
> how? I am still not all too familiar with CygWin and configure ...
Have you looked at my howto for building mingw cross compiler? That may
answer your question.
See http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
I've never tried building under cygwin, but in theory it should work just
as well as under Linux or other well supported Unix'y hosts.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-03-07 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-07 11:06 Kai-Uwe Rommel
[not found] ` < C125672D.00688D51.00@abraham.ars.de >
1999-03-07 21:30 ` Mumit Khan [this message]
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` Kai-Uwe Rommel
-- strict thread matches above, loose matches on Subject: below --
1999-03-07 9:23 Kai-Uwe Rommel
[not found] ` < C125672D.005EA18F.00@abraham.ars.de >
1999-03-07 10:08 ` DJ Delorie
1999-03-31 19:45 ` DJ Delorie
1999-03-31 19:45 ` Kai-Uwe Rommel
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=199903080530.XAA21364@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=dj@delorie.com \
--cc=rommel@ars.de \
/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).