OS/390

2000-07-15 Thread pg
Hello, Autoconf, Browsing the CVS development tree at http://subversions.gnu.org/cgi-bin/cvsweb/autoconf/config.guess I see: *:OS/390:*:*) echo i370-ibm-openedition exit 0 ;; Of course I'm pleased to see that OS/390 is being recognized in a future autoconf. However, I see

re: "AIX" wackyness from Mo

2000-07-15 Thread Chris Abbey
Hey everyone, I'll fess up as the user Mo was referring to - but he missed a few key points... like this is happening on RedHat 6.2 not AIX. Here's the actual sequence of failures: [jikes@tweedle jikes]$ echo $PATH /opt/autoconf/bin:/opt/automake/bin:/opt/tcltk/bin:/usr/local/bin:/bin:/usr/bin:/u

New AC_CANONICAL_BUILD warning and AIX wackyness

2000-07-15 Thread Mo DeJong
I just did a CVS update and I am now getting this warning while running autoconf. ( last updated around 2000-07-06) % ./autogen.sh autoheader: src/config.h.in is unchanged configure.in:23: warning: AC_CANONICAL_BUILD invoked multiple times (line 23) dnl Set up host checks using config.sub an

Re: AC_DEFINE-descriptions with 2.14*

2000-07-15 Thread Johan Danielsson
[EMAIL PROTECTED] (Johan Danielsson) writes: > This doesn't work with newer autoconf since it explicitly checks for > ` and $. Isn't this infact a bug? AC_INIT(configure.in) AC_CONFIG_HEADER(config.h) zz=X AC_DEFINE_UNQUOTED($zz, 1, test) produces an empty config.h.in /Johan

AC_DEFINE-descriptions with 2.14*

2000-07-15 Thread Johan Danielsson
In 2.13 you could do stuff like: AC_DEFINE_UNQUOTED(`echo FOO`, 1, whatever) This doesn't work with newer autoconf since it explicitly checks for ` and $. So how should this be done? /Johan

Modifications/fixes to autoconf

2000-07-15 Thread Larry W. Virden
What is the preferred method of submitting changes to autoconf ? A friend has made some changes for me and I would like to submit them for inclusion in the upcoming autoconf release. However, I want to make sure they are submitted in the proper fashion, so that they are not rejected as being in