Re: AC_OBJEXT again

2000-12-12 Thread Akim Demaille
Here are the most relevant messages I have from earlier threads. -- * host or build characteristic? ** Earnie OBJEXT is only a build feature while EXEEXT is both a build feature and a host feature. ** Bernard answers Even m

Re: AC_OBJEXT again

2000-12-12 Thread Akim Demaille
| On Dec 7, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: | >> "Morten" == Morten Eriksen <[EMAIL PROTECTED]> writes: | Morten> Akim Demaille <[EMAIL PROTECTED]> writes: | >>> OBJEXT and EXEEXT [...] define precisely what they are (build, or | >>> host?), [...] | | Morten> Just wanted to a

OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Akim Demaille
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

Re: AC_OBJEXT again

2000-12-12 Thread Peter Eisentraut
Akim Demaille writes: > * host or build characteristic? It's neither, nor should it matter. It's a feature of the compiler. If there's an alternative Cygwin compiler that generates .com files, then that's what EXEEXT is. If there's a regular Unix compiler that generates a file 'foo.bazoo' whe

CVS Autotools

2000-12-12 Thread Akim Demaille
I'm happy to say that running the test suites of both Libtools and of Automake with CVS Autoconf works fine.

Re: AC_OBJEXT again

2000-12-12 Thread Alexandre Oliva
On Dec 12, 2000, Peter Eisentraut <[EMAIL PROTECTED]> wrote: > Akim Demaille writes: >> * host or build characteristic? > It's neither, nor should it matter. It's a feature of the compiler. I wholeheartedly agree. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red

Re: AC_OBJEXT again

2000-12-12 Thread Akim Demaille
> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes: Peter> Akim Demaille writes: >> * host or build characteristic? Peter> It's neither, nor should it matter. It's a feature of the Peter> compiler. If there's an alternative Cygwin compiler that Peter> generates .com files, then that'

Config error for Darwin (Mac OS/X)

2000-12-12 Thread Tim Power
I get a sed error, unescaped line termination character during the final stage of the ./configure on Darwin, it is trying to write the makefiles... has anyone found a solution to this? - Visit our Internet site at http://w

Re: AC_OBJEXT again

2000-12-12 Thread Alexandre Oliva
On Dec 12, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: > What you describe is precisely what I meant by `build': there is not a > single reference to the host in what you describe. Nope, the output of the compiler follows conventions of the host machine, so it's a characteristic of the host.

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Ralf Corsepius
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. >

Re: autoconf/161

2000-12-12 Thread Pavel Roskin
On 12 Dec 2000 [EMAIL PROTECTED] wrote: > The problem still exists in CVS in AC_LANG_SOURCE(C++) > It doesn't appear that the testsuite can catch this problem. What is really scary is that the testsuite doesn't test C++ at all (but it has few tests for Fortran 77). Is it intentional o

Re: AC_OBJEXT again

2000-12-12 Thread Akim Demaille
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> On Dec 12, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: >> What you describe is precisely what I meant by `build': there is >> not a single reference to the host in what you describe. Alexandre> Nope, the output of the

Re: AC_OBJEXT again

2000-12-12 Thread akim
On Tue, Dec 12, 2000 at 07:30:05PM +0100, Akim Demaille wrote: > > Alexandre> Such a cross-compiler would be a broken compiler. I don't > Alexandre> know of any such cross-compilers, so this point is moot. > > Ah!!! Then you are telling me we just don't care about __CYGWIN32__ > etc. Then tha

Re: AC_OBJEXT again

2000-12-12 Thread Alexandre Oliva
On Dec 12, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: > If the cross-compiler bar running under Unix still produces non .exe > by default, then we have to over ride its preference. Please find one such cross-compiler before speculating on their existence. All compilers I know of that genera

Re: AC_OBJEXT again

2000-12-12 Thread Alexandre Oliva
On Dec 12, 2000, [EMAIL PROTECTED] wrote: > EXEEXT and OBJEXT don't need to know $CYGWIN etc. Ok, but I'd rather have the macros renamed to either _AC_HOST_???EXT or _AC_CC_???EXT (and only test with the C compiler). But I'm also a bit unsure as to whether we should use _AC_LINK_I

Re: CVS Autotools

2000-12-12 Thread Raja R Harinath
Hi, Akim Demaille <[EMAIL PROTECTED]> writes: > I'm happy to say that running the test suites of both Libtools and of > Automake with CVS Autoconf works fine. The following simple configure.in seems to be causing problems, with the latest CVS libtool from the multi-language-branch, and CVS autoc

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Mo DeJong
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,

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Earnie Boyd
--- 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

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Mo DeJong
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

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Earnie Boyd
--- 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 --

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Alexandre Oliva
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

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Earnie Boyd
--- 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? > >

Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

2000-12-12 Thread Alexandre Oliva
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