Hello,
We're currently using GNU autoconf v2.50 on Solaris 2.6, but are preparing
to upgrade to Solaris 8. Can you please tell me if you provide a 32-bit and
64-bit version of GNU autoconf and for how long you plan on supporting them?
Thank you,
Maria E. Torok
NASA - CLCS COTS Software Coordinat
Anything you could tell me regarding 32-bit and 64-bit versions of automake,
make, and m4 would also be appreciated!
> -Original Message-
> From: Torok-1, Maria
> Sent: Wednesday, October 10, 2001 08:05 AM
> To: [EMAIL PROTECTED]
> Subject: GNU autoconf 32/64-bit Support
> "Bob" == Bob Proulx <[EMAIL PROTECTED]> writes:
Bob> It works for me in 2.52. I specifically upgraded to it for all
Bob> of the nice portability improvements and bug fixes that the folks
Bob> have been making in it. Especially those for HP-UX. [In case no
Bob> one said so before, Thanks!
> "John" == John Poltorak <[EMAIL PROTECTED]> writes:
John> I have just re-installed Autoconf v2.50 without GAWK on the PATH
John> and no AWK variable set. When attempting to build SED, autoconf
John> complains with:-
Why do you need Autoconf to build Sed?
John> autoconf.[753]: gawk: not fo
| > You'll need to call
| > AC_CHECK_PROGS(YACC, byacc yacc 'bison -y', [AM_MISSING_PROG(yacc)])
| > instead of using the undocumented, unsupported, internal am_missing_run
|
| That had worried me a little. Thanks for clarifying that.
It seems incorrect to me. AC_MISSING_PROG is a macro per
On Wed, Oct 10, 2001 at 03:52:38PM +0200, Akim Demaille wrote:
> > "John" == John Poltorak <[EMAIL PROTECTED]> writes:
>
> John> I have just re-installed Autoconf v2.50 without GAWK on the PATH
> John> and no AWK variable set. When attempting to build SED, autoconf
> John> complains with:-
>
"Torok-1, Maria" wrote:
>
> Anything you could tell me regarding 32-bit and 64-bit versions of automake,
> make, and m4 would also be appreciated!
> [..]
> > E-mail: [EMAIL PROTECTED]
"Torok-1, Maria" wrote:
> We're currently using GNU libtool v1.4 on Solaris 2.6,
... before you flood the mai
