public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Jon Leichter" <jon@symas.com>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <cygwin@cygwin.com>
Subject: RE: Compiling apps to Mingw32 with cygwin
Date: Thu, 10 Jan 2002 17:31:00 -0000	[thread overview]
Message-ID: <DLEBJKNCNLJEDKMKICHGEENPCBAA.jon@symas.com> (raw)
In-Reply-To: <05b801c19a3f$20199850$0200a8c0@lifelesswks>

> -----Original Message-----
> From: Robert Collins [mailto:robert.collins@itdomain.com.au]
> Sent: Thursday, January 10, 2002 5:27 PM
> To: Jon Leichter
> Cc: cygwin@cygwin.com
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> ----- Original Message -----
> From: "Jon Leichter" <jon@symas.com>
> To: "Robert Collins" <robert.collins@itdomain.com.au>
> Cc: <cygwin@cygwin.com>
> Sent: Friday, January 11, 2002 12:20 PM
> Subject: RE: Compiling apps to Mingw32 with cygwin
>
>
> > 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 is
> > deprecated. I assume, however, that it still works to some extent.
> >
> > I tried to configure with the following:
> >
> > $ ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32
> >
> > I've left --target off, since I know it will get the value of --host,
> which
> > is what I want. It does.
> >
> > First, some questions:
> >
> > - What is correct: i386-pc-mingw32 or i686-pc-mingw32? If one is
> correct,
> > why? If both are correct, how does one decide which one to use?
> >
> > - I notice that if I merely use --host=mingw32, config.guess will
> equate
> > "mingw32" as "i386-unknown-mingw32". Why?
> >
> > - Is there a plan to get "32" from "mingw32", i.e. "mingw"? Of course,
> that
> > won't be useful with old projects that still need the "32" to be
> present...
> > :(
> >
> > ===
> >
> > Now my results:
> >
> > - I never see configure look for i686-pc-mingw32-gcc. It merely picks
> up
> > 'gcc'. Any ideas why?
>
> Do you have an accessible i686-pc-mingw32-gcc ?
>
> have a look at the configure script - it may provide some clues :}.
>
> Rob
>

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.

Jon



--
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/

  reply	other threads:[~2002-01-11  1:31 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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] <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
     [not found] <3C3C999C.E7DBD5CC@yahoo.com>
2002-01-09 11:42 ` Earnie Boyd
     [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=DLEBJKNCNLJEDKMKICHGEENPCBAA.jon@symas.com \
    --to=jon@symas.com \
    --cc=cygwin@cygwin.com \
    --cc=robert.collins@itdomain.com.au \
    /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).