Re: automatic cross compiler search patch

[Akim Demaille]

> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:

Alexandre> So, how about setting both of host and host_alias from the
Alexandre> command-line arguments, just for the sake of backward
Alexandre> compatibility?  We should still recommend the use of
Alexandre> *_alias before AC_CANONICAL_ (and we might even warn about
Alexandre> uses of them, by AU_DEFUNing them to *_alias and arranging
Alexandre> for AC_CANONICAL_* to undefine them).

:) :) :)  You seem to really enjoy AU_DEFUN, don't you :)

Well, I'm OK with letting host = host_alias before AC_CANON, but
really I don't like it at all.  It is giving a loaded gun to the user
pointing him to his foot.

I'll try to setup the AU_DEFUN trick later, in a different patch.
I'll apply this one with host=host_alias etc. at the end of the option
handling.

Akim

Re: acgeneral.m4 & unsupported case patterns

[Akim Demaille]

> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:

Akim>expr has a bad reputation

Paul> Its syntax is awkward -- was that what you were thinking about?

Nope, I was referring to the portability.  And precisely about the
syntax, is `match string expr' portable?

Paul> expr is already mentioned in the GNU coding standards as a
Paul> utility that you can use.

OK, thanks!

Paul> if expr "x$ac_package" : '.*[^-a-zA-Z0-9_]' >/dev/null; then

My understanding of the `x' here is to avoid problems with $ac_package
being a built-in of expr, right?  BTW, what is the right spelling?
Built-in, builtin, built in.  What is the plural?

Akim

Re: automatic cross compiler search patch

[Alexandre Oliva]

On May 24, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:

> I'll try to setup the AU_DEFUN trick later, in a different patch.

Ok

> I'll apply this one with host=host_alias etc. at the end of the option
> handling.

Thanks,

-- 
Alexandre OlivaEnjoy Guaraná, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat companyaoliva@{redhat, cygnus}.com
Free Software Developer and EvangelistCS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me

Re: acgeneral.m4 & unsupported case patterns

[Earnie Boyd]

--- Akim Demaille <[EMAIL PROTECTED]> wrote:
-8<-
> BTW, what is the right spelling?
> Built-in, builtin, built in.  What is the plural?
> 

My 1963 Webster's Dictionary says that it's built-in and an adjective which
means that it's not a noun so therefore doesn't have a plural.  It would be
built-in option or built-in options.  As for the dash, it is common practice to
use builtin instead of built-in.

Cheers,

=
---
   Earnie Boyd: 
__Cygwin: POSIX on Windows__
Cygwin Newbies: 
   __Minimalist GNU for Windows__
  Mingw32 List: 
Mingw Home: 

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Akim Demaille]

Currently to find out if we are under one of these environments
configure runs a compilation, typically to see if __CYGWIN__ is
defined etc.

Can't we do this kind of checks *without* compiling?  IIUC correctly,
for Autoconf to be really DJGPP aware, we'd need to change things
which do not depend upon compilation, so it is somewhat unfortunate.

Anybody would have solutions to provide?

Akim

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Eli Zaretskii]

On 24 May 2000, Akim Demaille wrote:

> Currently to find out if we are under one of these environments
> configure runs a compilation, typically to see if __CYGWIN__ is
> defined etc.
> 
> Can't we do this kind of checks *without* compiling?

For DJGPP, you can look for the variable DJDIR in the environment.  Any 
DJGPP program gets this pushed into its environment by the startup code, 
and Bash and/or M4 are no exception.

In addition, Bash will have the OS-identifier variable (I forget the 
name) which will match the string "msdosdjgpp".

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Earnie Boyd]

--- Akim Demaille <[EMAIL PROTECTED]> wrote:
> 
> Currently to find out if we are under one of these environments
> configure runs a compilation, typically to see if __CYGWIN__ is
> defined etc.
> 
> Can't we do this kind of checks *without* compiling?  IIUC correctly,
> for Autoconf to be really DJGPP aware, we'd need to change things
> which do not depend upon compilation, so it is somewhat unfortunate.
> 
> Anybody would have solutions to provide?
> 

Cygwin comes with uname which reports:
CYGWIN_NT-4.0 DU147636 1.1.0(0.17/3/2) 2000-03-01 00:15:19 i686 unknown

For MinGW I have a uname hack which reports:
MINGW_WinNT DU147636 3 0 i686 unknown

Cheers,

=
---
   Earnie Boyd: 
__Cygwin: POSIX on Windows__
Cygwin Newbies: 
   __Minimalist GNU for Windows__
  Mingw32 List: 
Mingw Home: 

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Eli Zaretskii]

On Wed, 24 May 2000, Earnie Boyd wrote:

> Cygwin comes with uname which reports:
> CYGWIN_NT-4.0 DU147636 1.1.0(0.17/3/2) 2000-03-01 00:15:19 i686 unknown
> 
> For MinGW I have a uname hack which reports:
> MINGW_WinNT DU147636 3 0 i686 unknown

Sounds a bit dangerous to me: what if someone uses Mingw, but uname is 
from Cygwin?  I understand that many Mingw developers use Cygwin 
toolchain (except the compiler and Binutils).

How about running "gcc -v --version" and looking at the output?

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Alexandre Oliva]

On May 24, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:

> Anybody would have solutions to provide?

How about something like (totally untested):

if (cd c:\\ && cd .. && test `pwd` = "C:\\") 2> /dev/null

-- 
Alexandre OlivaEnjoy Guaraná, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat companyaoliva@{redhat, cygnus}.com
Free Software Developer and EvangelistCS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Earnie Boyd]

--- Eli Zaretskii <[EMAIL PROTECTED]> wrote:
> 
> On Wed, 24 May 2000, Earnie Boyd wrote:
> 
> > Cygwin comes with uname which reports:
> > CYGWIN_NT-4.0 DU147636 1.1.0(0.17/3/2) 2000-03-01 00:15:19 i686 unknown
> > 
> > For MinGW I have a uname hack which reports:
> > MINGW_WinNT DU147636 3 0 i686 unknown
> 
> Sounds a bit dangerous to me: what if someone uses Mingw, but uname is 
> from Cygwin?  I understand that many Mingw developers use Cygwin 
> toolchain (except the compiler and Binutils).
> 
> How about running "gcc -v --version" and looking at the output?
> 

There is full email support for MinGW users, see my .sig.  Also, most MinGW
users are using it for Win32 native developement and aren't really doing
./configure.  Some are, and those that are know how to make it work.  Also, the
http://www.mingw.org page has a nice FAQ which can be modified as needed.

The current version of config.guess/sub without modification return
i686-pc-mingw32 for my configuration and returns i686-pc-cygwin for my Cygwin
configuration.

BTW, gcc --version only return 2.95.2 and gcc -v does contain the characters
mingw when returning the name of the specs file; but I don't like this.

Regards,

=
---
   Earnie Boyd: 
__Cygwin: POSIX on Windows__
Cygwin Newbies: 
   __Minimalist GNU for Windows__
  Mingw32 List: 
Mingw Home: 

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Re: acgeneral.m4 & unsupported case patterns

[Felix Lee]

Akim Demaille <[EMAIL PROTECTED]> wrote:
> BTW, what is the right spelling?
> Built-in, builtin, built in.  What is the plural?

www.m-w.com says 'built-in'.  elision of hyphens is typical
in language evolution, so 'builtin' may eventually become
'normal' english.

no special plural noted for the noun form, so 'built-ins'.
--

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Earnie Boyd]

--- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> On May 24, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> 
> > Anybody would have solutions to provide?
> 
> How about something like (totally untested):
> 
> if (cd c:\\ && cd .. && test `pwd` = "C:\\") 2> /dev/null
> 

NO!!  That is shell dependent.  Yuck, yuck, yuck.

Regards,

=
---
   Earnie Boyd: 
__Cygwin: POSIX on Windows__
Cygwin Newbies: 
   __Minimalist GNU for Windows__
  Mingw32 List: 
Mingw Home: 

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Alexandre Oliva]

On May 24, 2000, Earnie Boyd <[EMAIL PROTECTED]> wrote:

> --- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
>> On May 24, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> 
>> > Anybody would have solutions to provide?

>> How about something like (totally untested):

>> if (cd c:\\ && cd .. && test `pwd` = "C:\\") 2> /dev/null

> NO!!  That is shell dependent.  Yuck, yuck, yuck.

We can test several alternatives.  Is there anything wrong with the
general approach?

-- 
Alexandre OlivaEnjoy Guaraná, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat companyaoliva@{redhat, cygnus}.com
Free Software Developer and EvangelistCS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Eli Zaretskii]

On 24 May 2000, Alexandre Oliva wrote:

> How about something like (totally untested):
> 
> if (cd c:\\ && cd .. && test `pwd` = "C:\\") 2> /dev/null

This should work with any DOS/Windows environment, it's not specific to 
any of the three (DJGPP, Mingw, or Cygwin).  So it cannot reliably 
distinguish between these three.

In addition, `pwd' will report "c:/", at least with the DJGPP port of 
Bash.

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Earnie Boyd]

BTW, since your supporting MinGW, the IFS value when searching the PATH needs
to be ';' instead of ':'.

Cheers,

=
---
   Earnie Boyd: 
__Cygwin: POSIX on Windows__
Cygwin Newbies: 
   __Minimalist GNU for Windows__
  Mingw32 List: 
Mingw Home: 

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Eli Zaretskii]

On Wed, 24 May 2000, Earnie Boyd wrote:

> > > Cygwin comes with uname which reports:
> > > CYGWIN_NT-4.0 DU147636 1.1.0(0.17/3/2) 2000-03-01 00:15:19 i686 unknown
> > > 
> > > For MinGW I have a uname hack which reports:
> > > MINGW_WinNT DU147636 3 0 i686 unknown
> > 
> > Sounds a bit dangerous to me: what if someone uses Mingw, but uname is 
> > from Cygwin?  I understand that many Mingw developers use Cygwin 
> > toolchain (except the compiler and Binutils).
> 
> There is full email support for MinGW users, see my .sig.  Also, most MinGW
> users are using it for Win32 native developement and aren't really doing
> ./configure.  Some are, and those that are know how to make it work.  Also, the
> http://www.mingw.org page has a nice FAQ which can be modified as needed.

Sorry, I don't follow: how does this help to detect whether Autoconf is 
being built for Cygwin or for Mingw?

Or are you saying that this distinction is not necessary?

> BTW, gcc --version only return 2.95.2 and gcc -v does contain the characters
> mingw when returning the name of the specs file; but I don't like this.

Sure, that's why I suggested both (on the assumption that the version 
info might be useful in some cases; if not, it can be easily ignored).

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Earnie Boyd]

--- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> On May 24, 2000, Earnie Boyd <[EMAIL PROTECTED]> wrote:
> 
> > --- Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> >> On May 24, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> >> 
> >> > Anybody would have solutions to provide?
> 
> >> How about something like (totally untested):
> 
> >> if (cd c:\\ && cd .. && test `pwd` = "C:\\") 2> /dev/null
> 
> > NO!!  That is shell dependent.  Yuck, yuck, yuck.
> 
> We can test several alternatives.  Is there anything wrong with the
> general approach?
> 

Yes, C: isn't guaranteed to be a valid device.  It's not specific to djgpp,
cygwin or mingw.

Cheers,

=
---
   Earnie Boyd: 
__Cygwin: POSIX on Windows__
Cygwin Newbies: 
   __Minimalist GNU for Windows__
  Mingw32 List: 
Mingw Home: 

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Earnie Boyd]

--- Eli Zaretskii <[EMAIL PROTECTED]> wrote:
> 
> On Wed, 24 May 2000, Earnie Boyd wrote:
> 
> > > > Cygwin comes with uname which reports:
> > > > CYGWIN_NT-4.0 DU147636 1.1.0(0.17/3/2) 2000-03-01 00:15:19 i686 unknown
> > > > 
> > > > For MinGW I have a uname hack which reports:
> > > > MINGW_WinNT DU147636 3 0 i686 unknown
> > > 
> > > Sounds a bit dangerous to me: what if someone uses Mingw, but uname is 
> > > from Cygwin?  I understand that many Mingw developers use Cygwin 
> > > toolchain (except the compiler and Binutils).
> > 
> > There is full email support for MinGW users, see my .sig.  Also, most MinGW
> > users are using it for Win32 native developement and aren't really doing
> > ./configure.  Some are, and those that are know how to make it work.  Also,
> the
> > http://www.mingw.org page has a nice FAQ which can be modified as needed.
> 
> Sorry, I don't follow: how does this help to detect whether Autoconf is 
> being built for Cygwin or for Mingw?
> 

Oh, I'm just saying that for people having this type of problems there is a way
to find the answer.

> Or are you saying that this distinction is not necessary?
> 

For those using the Cygwin compiler toolset for MinGW, yes the distinction
between Cygwin and MinGW isn't necessary, the environment is Cygwin even if the
compiler set is the MinGW set.

There a those, me included, using Amol's port of zsh to WinNT with a native
build of fileutils, textutils and the like, this is where the MinGW distinction
is going to matter.

IMO, treat detecting Cygwin and MinGW as you would for "normal" unix.  The
result will need to set special variables such as ac_exeext.


=
---
   Earnie Boyd: 
__Cygwin: POSIX on Windows__
Cygwin Newbies: 
   __Minimalist GNU for Windows__
  Mingw32 List: 
Mingw Home: 

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Re: autoconf-1.4

[Gordon Matzigkeit]

> Emmanuel Dreyfus writes:

 ED> I need to get autoconf-1.4. Because this release is rather
 ED> old, I can't find it anymore on the Internet. Getting it from the
 ED> CVS is therefore my idea, but I can't figure out what tag should
 ED> I checkout. Please help!

That's something that only the Autoconf hackers would be able to tell
you.  I've cc'ed this message to [EMAIL PROTECTED]

-- 
 Gordon Matzigkeit <[EMAIL PROTECTED]>  //\ I'm a FIG (http://fig.org/)
Committed to freedom and diversity \// I use GNU (http://www.gnu.org/)

Re: Detecting DJGPP, Cygwin, Mingwin and EMX OS/2

[Felix Lee]

Alexandre Oliva <[EMAIL PROTECTED]>:
> if (cd c:\\ && cd .. && test `pwd` = "C:\\") 2> /dev/null

there doesn't have to be a c:.  I've seen a system where the
only disk is a hard drive named a:.
--