> -Original Message-
> From: Akim Demaille [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 13, 2000 1:43 PM
> To: Mo DeJong
> Cc: [EMAIL PROTECTED]
> Subject: Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)
>
>
> >>>>> &q
> -Original Message-
> From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 13, 2000 2:02 AM
> To: Alexandre Oliva; Mo DeJong
> Cc: [EMAIL PROTECTED]
> Subject: Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)
>
>
> --- Alexan
--- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> On Dec 12, 2000, Earnie Boyd <[EMAIL PROTECTED]> wrote:
>
> > --- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> >> On Dec 12, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> >>
> >> > I guess the question is, should we try to compile something and the
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> But would this still work if I wanted to compile with the mingw
Mo> compiler under Cygwin? The mingw native compiler is also named
Mo> gcc, so what --host triple would I need to pass to the configure
Mo> script? It seems like I would need to
On Dec 12, 2000, Earnie Boyd <[EMAIL PROTECTED]> wrote:
> --- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
>> On Dec 12, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>>
>> > I guess the question is, should we try to compile something and the
>> > set the $host if the user did not, or do we just expe
--- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> On Dec 12, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>
> > I guess the question is, should we try to compile something and the
> > set the $host if the user did not, or do we just expect that the
> > user is going to pass the correct --host?
>
>
On Dec 12, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> I guess the question is, should we try to compile something and the
> set the $host if the user did not, or do we just expect that the
> user is going to pass the correct --host?
Methinks config.guess should do it. Can't it tell cygwin fro
--- Mo DeJong <[EMAIL PROTECTED]> wrote:
> On Tue, 12 Dec 2000, Earnie Boyd wrote:
>
> > --- Mo DeJong <[EMAIL PROTECTED]> wrote:
> > >
> > > But would this still work if I wanted to compile with
> > > the mingw compiler under Cygwin? The mingw native
> > > compiler is also named gcc, so what --
On Tue, 12 Dec 2000, Earnie Boyd wrote:
> --- Mo DeJong <[EMAIL PROTECTED]> wrote:
> >
> > But would this still work if I wanted to compile with
> > the mingw compiler under Cygwin? The mingw native
> > compiler is also named gcc, so what --host triple
> > would I need to pass to the configure s
--- Mo DeJong <[EMAIL PROTECTED]> wrote:
>
> But would this still work if I wanted to compile with
> the mingw compiler under Cygwin? The mingw native
> compiler is also named gcc, so what --host triple
> would I need to pass to the configure script? It
> seems like I would need to pass something
On 12 Dec 2000, Akim Demaille wrote:
> I don't think we need the test we used to perform (compiling and
> checking for the names the compiler leaves around). But if we want to
> run this test, then only when not cross-compiling.
>
> There are other things which might be considered. After all,
Akim Demaille wrote:
>
> Maybe we should just make the difference between cross-compilation or
> not? Here is what I propose.
>
> 1. AC_INIT uses uname to compute CYGWIN32, MINGW32 and EMXOS2,
>hence OBJEXT and EXEEXT.
>
> 2. AC_LANG_COMPILER if cross-compiling runs the old Cygwin32 etc.
>
Maybe we should just make the difference between cross-compilation or
not? Here is what I propose.
1. AC_INIT uses uname to compute CYGWIN32, MINGW32 and EMXOS2,
hence OBJEXT and EXEEXT.
2. AC_LANG_COMPILER if cross-compiling runs the old Cygwin32 etc.
tests which involve a compilation
13 matches
Mail list logo
