From: Earnie Boyd <earnie_boyd@yahoo.com>
To: CU List <Cygwin@Cygwin.Com>
Subject: Re: Compiling apps to Mingw32 with cygwin
Date: Wed, 09 Jan 2002 11:42:00 -0000 [thread overview]
Message-ID: <3C3C9D05.D603F7F5@yahoo.com> (raw)
In-Reply-To: <3C3C999C.E7DBD5CC@yahoo.com>
> Subject: Re: Compiling apps to Mingw32 with cygwin
> Date: Wed, 9 Jan 2002 18:11:16 +0100
> From: "J. Henning Schwentner" <hschwentner@yahoo.com>
> To: cygwin@cygwin.com
>
> Am Montag, 7. Januar 2002 17:49 schrieben Sie:
> > Jon Leichter wrote:
> > > - Using CC="gcc -mno-cygwin" is good for compiling, but it's bad for GNU
> > > Libtool, as I have mentioned. I use a wrapper script: CC=mgcc. What do
> > > you think of this Earnie?
> >
> > Your wrapper script is a good idea but has the wrong name as has been
> > pointed out already. It needs to be named i386-pc-mingw32-gcc and a
> > copy as mingw32-gcc so that when specifying the --host=mingw32 or
> > --host=i386-pc-mingw32 the configure script will find it appropriately.
> > Of course to do this you also need to do the same for the binutils
> > binaries.
>
> Do the binutils also support the -mno-cygwin switch?
I'll leave that as an exercise for you to figure out.
> Or can the
> 386-pc-mingw32-<binutilname> files be simple links to the cygwin versions?
>
Yes, simply symlink will do.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next parent reply other threads:[~2002-01-09 19:42 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C3C999C.E7DBD5CC@yahoo.com>
2002-01-09 11:42 ` Earnie Boyd [this message]
[not found] <3C3EDCA7.C40E3CD6@yahoo.com>
2002-01-11 5:12 ` Earnie Boyd
2002-01-11 5:33 ` Robert Collins
[not found] <3C3ED90B.F0B81A47@yahoo.com>
2002-01-11 4:43 ` Earnie Boyd
2002-01-10 1:39 Bernard Dautrevaux
2002-01-10 13:09 ` Jon Leichter
2002-01-10 13:43 ` Robert Collins
2002-01-10 14:05 ` Charles Wilson
2002-01-10 14:06 ` Jon Leichter
2002-01-10 14:29 ` Robert Collins
2002-01-10 16:25 ` Jon Leichter
2002-01-10 14:31 ` Earnie Boyd
2002-01-10 14:40 ` Robert Collins
2002-01-10 16:18 ` Jon Leichter
2002-01-10 16:28 ` Robert Collins
2002-01-10 17:19 ` Jon Leichter
2002-01-10 17:27 ` Robert Collins
2002-01-10 17:31 ` Jon Leichter
2002-01-10 17:44 ` Robert Collins
2002-01-10 17:50 ` Jon Leichter
2002-01-10 17:52 ` Robert Collins
2002-01-10 17:58 ` Christopher Faylor
2002-01-10 17:59 ` Robert Collins
2002-01-10 18:11 ` Jon Leichter
2002-01-10 18:16 ` Robert Collins
2002-01-10 18:23 ` Jon Leichter
2002-01-10 18:25 ` Robert Collins
2002-01-10 18:28 ` Jon Leichter
2002-01-10 16:34 ` Charles Wilson
2002-01-11 4:11 ` Earnie Boyd
2002-01-11 10:35 ` Jon Leichter
2002-01-12 12:51 ` Earnie Boyd
2002-01-12 15:29 ` Robert Collins
2002-01-13 10:44 ` Jon Leichter
2002-01-13 12:39 ` Robert Collins
2002-01-13 20:17 ` Jon Leichter
2002-01-14 0:53 ` Robert Collins
2002-01-14 6:09 ` Earnie Boyd
2002-01-14 5:51 ` Earnie Boyd
2002-01-14 10:48 ` Jon Leichter
2002-01-12 15:27 ` Robert Collins
[not found] <3C391A0A.758D073@yahoo.com>
2002-01-07 6:29 ` Earnie Boyd
2002-01-07 8:34 ` Jon Leichter
2002-01-07 8:49 ` Earnie Boyd
2002-01-07 11:44 ` J. Henning Schwentner
2002-01-09 9:09 ` J. Henning Schwentner
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 6:24 Bernard Dautrevaux
[not found] <200201061357.IAA27856@zealous.cnchost.com>
2002-01-06 9:55 ` Jon Leichter
[not found] <200201051541.KAA10021@irresistable.cnchost.com>
2002-01-05 11:38 ` Jon Leichter
2002-01-06 5:55 ` J. Henning Schwentner
[not found] ` <ITDOMAIN003sl3xbYiM0000006c@itdomain003.itdomain.net.au>
2002-01-06 13:47 ` Robert Collins
2002-01-05 7:40 J. Henning Schwentner
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=3C3C9D05.D603F7F5@yahoo.com \
--to=earnie_boyd@yahoo.com \
--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).