> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Earnie Boyd
> Sent: Monday, January 14, 2002 5:43 AM
> To: Robert Collins
> Cc: Jon Leichter; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with c
Jon Leichter wrote:
>
>
> > > Using Robert's invocation WOULD put configure in cross-compile mode.
> > But
> > > since using Cygwin GCC to generate MinGW is ALMOST like a
> > cross-compile, it
> > > will work out ok. In fact, one compelling reason to use Robert's
> > method is
> > > because one
Robert Collins wrote:
>
> - Original Message -
> From: "Earnie Boyd" <[EMAIL PROTECTED]>
> > 1) `gcc -mno-cygwin' is not a cross compile.
> > 2) it is possible to emulate a cross build system using a scripted
> `gcc
> > -mno-cygwin' and symlinks.
> > 3) `gcc -mno-cygwin' switches the bu
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> Grrr... This makes one start believing that Earnie's method is more
correct.
> I suppose the right answer to this question is: use whichever method
seems
> to work best for the project that you're working on. If they both wor
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Robert Collins
> Sent: Sunday, January 13, 2002 12:31 PM
> To: Jon Leichter; Earnie Boyd
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps t
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> First off... thanks again to both Robert and Earnie for taking part in
this
> discussion. I appreciate it a lot.
>
> Recapping once again...
>
> Robert says to use:
>
> $ ./configure --host=i686-pc-mingw32 --build=i686-pc-
lto:[EMAIL PROTECTED]]On Behalf
> Of Robert Collins
> Sent: Saturday, January 12, 2002 3:28 PM
> To: Earnie Boyd; Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> - Original Message -
> From: "Earnie
- Original Message -
From: "Earnie Boyd" <[EMAIL PROTECTED]>
> 1) `gcc -mno-cygwin' is not a cross compile.
> 2) it is possible to emulate a cross build system using a scripted
`gcc
> -mno-cygwin' and symlinks.
> 3) `gcc -mno-cygwin' switches the build environment from Cygwin to
> MinGW.
===
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
>
> Earnie and Robert,
>
> I'm a bit confused when I consider the commentary that you both have
> contributed on this topic. Here's what I have assessed. You two guys
correct
> me where I'm wrong.
>
> ===
>
> Robert has im
Jon Leichter wrote:
>
> Earnie. Your comments seem to contradict each other. In your last email, it
> seems you are implying that "gcc -mno-cygwin" is NOT a cross-compile. And
> then you went on to explain how I could safely use the switches if I set
> symlinks to emulate a cross-compile. Which p
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Earnie Boyd
> Sent: Friday, January 11, 2002 4:01 AM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
&
===
- Original Message -
From: "Earnie Boyd" <[EMAIL PROTECTED]>
>
> This rule is changed for 2.50 and greater. Build no longer takes on
the
> value of host and you're warned about this when specifying --host
> without specifying --build. IIRC, if you specify build without host
> then h
> Subject: Re: Compiling apps to Mingw32 with cygwin
> Date: Fri, 11 Jan 2002 13:25:17 +1100
> From: "Robert Collins" <[EMAIL PROTECTED]>
> To: "Jon Leichter" <[EMAIL PROTECTED]>
> CC: <[EMAIL PROTECTED]>
>
> - Original Message -
> Subject: RE: Compiling apps to Mingw32 with cygwin
> Date: Thu, 10 Jan 2002 17:20:42 -0800
> From: "Jon Leichter" <[EMAIL PROTECTED]>
> To: "Robert Collins" <[EMAIL PROTECTED]>
> CC: <[EMAIL PROTECTED]>
>
> Ok. I need to return to a
Jon Leichter wrote:
>
> > -Original Message-
> > From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, January 10, 2002 2:31 PM
> > To: Jon Leichter
> > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: Re: Compiling apps to Ming
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 6:25 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> - Original Message -
> From: "
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> > See above why it doesn't. mingw != cygwin :}.
>
> If 'build' WERE to be tested automatically, independent to 'host', it
would
> come up with 'i686-pc-cygwin'. Thus, we'd effectively end up with the
same
> line you specified
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 6:16 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> - Original Message -
> From: &q
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> Thus... returning to the ORIGINAL topic of this thread... I had
recommended
> the following to the OP:
>
> $ env CC=mgcc ./configure --host=i686-pc-mingw32
>
> My new understanding of switches gives me new perspective. 'buil
;, but it WILL work.
This whole thread went off on a tangent suggesting that my solution was
wrong. So tell me. If my solution works more often than the "proper" one,
how is it wrong?
Jon
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Se
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> >Ouchies. I agree - yet another reason for cygwin ports to be updated
> >by the maintainer :}.
package/port
^^^
> If I am reading this correctly, this is not really a cygwin issue.
It's
> a cros
On Fri, Jan 11, 2002 at 12:52:01PM +1100, Robert Collins wrote:
>- Original Message -
>From: "Jon Leichter" <[EMAIL PROTECTED]>
>
>>AC_CHECK_TOOL checks for tools with a ${host} prefix. AC_CHECK_PROG
>>does not.
>>
>>In my opinion, this serves as another example that one cannot count on
>
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> AC_CHECK_TOOL checks for tools with a ${host} prefix. AC_CHECK_PROG
does
> not.
>
> In my opinion, this serves as another example that one cannot count on
a
> configure script being up-to-date.
Ouchies. I agree - yet another
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 5:45 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> - Original Message -
> From: "
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> Sorry... I left that out. Yes, I do have an accessible
i686-pc-mingw32-gcc,
> and I am looking at the configure script. It just searches for gcc. It
> doesn't bother to look for the prefixed tool.
Are you sure? Here's the out
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 5:27 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> - Original Message -
> From: &q
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
To: "Robert Collins" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, January 11, 2002 12:20 PM
Subject: RE: Compiling apps to Mingw32 with cygwin
> Ok. I need to re
Ok. I need to return to asking some questions with my new understanding
of --build, --host, and --target (which I'm incredibly grateful for and
happy about).
I have returned to working with OpenLDAP. The configure script is generated
with autconf-2.13.1. It uses AC_CANONICAL_SYSTEM, which you say
Jon Leichter wrote:
> It's true that I don't usually patch the script myself and send it back. In
> some cases, there isn't any organization to send the patches back to, e.g.
> GDBM. This is not an unsubstaniated statement. I sent patches to GDBM years
> ago, and nothing ever came of it.
What
===
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> I still don't understand why I'd want to symlink the binutils
binaries. I
> WANT the Cygwin binutils. They don't generate object code; they
operate on
> it. The Cygwin binutils do a fine job (as Cygwin binaries) operating
PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> - Original Message -
> From: "Jon Leichter" <[EMAIL PROTECTED]>
>
> > > No. Specify --host. The meaning is clearly docume
> -Original Message-
> From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 2:31 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> Using `gcc -mno-cygwin' is sw
===
- Original Message -
From: "Earnie Boyd" <[EMAIL PROTECTED]>
> My statements are based on the standard. For those packages
conforming
> to AC_CAN0NICAL_SYSTEM my statements will make a difference. I'm
saying
> you should just get used to always doing it that way so that you never
>
Jon Leichter wrote:
>
> Earnie Boyd wrote:
> > 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 config
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
> > No. Specify --host. The meaning is clearly documented in the
autoconf
> > documentation.
> > For clarity:
> > build - what OS the compilation is running on..
> > host - what OS the binaries created should run on.
> > targe
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Robert Collins
> Sent: Thursday, January 10, 2002 1:44 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> Autoconf
Robert Collins wrote:
> No. Specify --host. The meaning is clearly documented in the autoconf
> documentation.
> For clarity:
> build - what OS the compilation is running on..
> host - what OS the binaries created should run on.
> target - what OS the binaries created should target their output
- Original Message -
From: "Jon Leichter" <[EMAIL PROTECTED]>
I hope I don't repeat anything from this thread, I've only been scanning
it lightly.
..
> obvious to me that unless you're building a project with a configure
script
> built by an up-to-date version of autoconf, none of what y
Earnie Boyd wrote:
> 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 appropria
> -Original Message-
> From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 09, 2002 8:42 PM
> To: CU List
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> > Subject: Re: Compiling apps to Mingw32 with cygwin
> > Date: Wed, 9
> Subject: Re: Compiling apps to Mingw32 with cygwin
> Date: Wed, 9 Jan 2002 18:11:16 +0100
> From: "J. Henning Schwentner" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
>
> Am Montag, 7. Januar 2002 17:49 schrieben Sie:
> > Jon Leichter wrote:
> &
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
Dear Earnie,
I do not get it with the --build switch. Am I not building on i686-pc-cygwin?
Is it i368-pc-mingw because I use the mingw-headers? But I use the
cygwin-compiler.
Sorry, but I am confused a bit ...
> Your wrapper script is a good idea but has the wrong name as has been
> pointed
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
for GNU
Libtool, as I have mentioned. I use a wrapper script: CC=mgcc. What do you
think of this Earnie?
Jon
> -Original Message-
> From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 07, 2002 6:29 AM
> To: CU List
> Cc: Jon Leichter; J. Henning Schwentn
> Subject: RE: Compiling apps to Mingw32 with cygwin
> Date: Sat, 5 Jan 2002 11:35:14 -0800
> From: "Jon Leichter" <[EMAIL PROTECTED]>
> Reply-To: "Jon Leichter" <[EMAIL PROTECTED]>
> To: "J. Henning Schwentner" <[EMAIL PROTECTED]&
> -Original Message-
> From: J. Henning Schwentner [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 06, 2002 2:57 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> Thanks for your quick help, this works nice!
>
> But,
- Original Message -
From: "J. Henning Schwentner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 07, 2002 12:57 AM
Subject: Re: Compiling apps to Mingw32 with cygwin
> Thanks for your quick help, this works nice!
>
> But, it is a
Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of J. Henning Schwentner
> Sent: Sunday, January 06, 2002 5:57 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> Thanks for your quick help, this works nice!
>
&g
Thanks for your quick help, this works nice!
But, it is a bit difficult. I think ideally configure should detect
--host=mingw32 --build=cygwin and in this case should add --mno-cygwin to
CFLAGS and CPPFLAGS (and do something to fix libtool).
I am not sure if this is a bit off topic, maybe this
Hi Henning.
You can use Cygwin's GCC. It's just a little more involved. Here's a short
answer. When you configure, do so like this:
$ env CC="gcc -mno-cygwin" ./configure --host=i386-pc-mingw32
Notice that your --host specification was a little off. The way that I have
specified it is t
51 matches
Mail list logo
