On Wed, Jul 21, 2004 at 07:16:50AM -0400, Dossy wrote:
Everyone,
I'd like to change the required version of autoconf required --
currently, AOLserver configure.in works with autoconf 2.13, but I'd like
to move to configure.ac and autoconf 2.50+.
Does anyone have any issues with this?
For
Everyone,
I'd like to change the required version of autoconf required --
currently, AOLserver configure.in works with autoconf 2.13, but I'd like
to move to configure.ac and autoconf 2.50+.
Does anyone have any issues with this?
-- Dossy
--
Dossy Shiobara mail: [EMAIL
Many relatively old (but not ancient) Linux distributions ship with
autoconf 2.13 such as RedHat 7.2, 7,3 and AS 2.1. Upgrading isn't
particularly painful but many only like using official rpms and AFAIK
RedHat does not provide them.
What is the advantage of upgrade?
rob
Dossy wrote:
Everyone,
I'd
On 2004.07.21, Rob Crittenden [EMAIL PROTECTED] wrote:
Many relatively old (but not ancient) Linux distributions ship with
autoconf 2.13 such as RedHat 7.2, 7,3 and AS 2.1. Upgrading isn't
particularly painful but many only like using official rpms and AFAIK
RedHat does not provide them.
Dossy wrote:
I'd like to change the required version of autoconf required --
currently, AOLserver configure.in works with autoconf 2.13, but I'd like
to move to configure.ac and autoconf 2.50+.
Does anyone have any issues with this?
Note that the Tcl core made the move to 2.50+ in 8.5 (the dev
At Wednesday 07:23 AM 7/21/2004, you wrote:
On 2004.07.21, Rob Crittenden [EMAIL PROTECTED] wrote:
Many relatively old (but not ancient) Linux distributions ship with
autoconf 2.13 such as RedHat 7.2, 7,3 and AS 2.1. Upgrading isn't
particularly painful but many only like using official rpms
On 2004.07.21, Jeff Hobbs [EMAIL PROTECTED] wrote:
Note that the Tcl core made the move to 2.50+ in 8.5 (the dev head).
This is another reason to upgrade AOLserver to use autoconf 2.50+ --
since AOLserver's build uses Tcl's build as a basis, until we switch
AOLserver to use autoconf 2.50+, we
Note that the Tcl core made the move to 2.50+ in 8.5 (the dev head).
This is another reason to upgrade AOLserver to use autoconf
2.50+ -- since AOLserver's build uses Tcl's build as a basis,
until we switch AOLserver to use autoconf 2.50+, we may not
be able to build AOLserver against Tcl
On 2004.07.21, John Caruso [EMAIL PROTECTED] wrote:
http://www.redhat.com/swr/noarch/autoconf-2.57-3.noarch.html
That's a RedHat 9 RPM, not an Advanced Server 2.1 RPM.
Excuse my RedHat ignorance, but could you explain the difference? Will
this RPM not install on RHAS 2.1 at all? Is it
On 2004.07.21, Jeff Hobbs [EMAIL PROTECTED] wrote:
I don't see why that's an issue really - only if you ever need
to regenerate the core Tcl stuff. It comes with a ready-made
configure that should work for AOLServer build variants.
At some point, AOLserver's build was relying on Tcl source.
At Wednesday 11:40 AM 7/21/2004, you wrote:
On 2004.07.21, John Caruso [EMAIL PROTECTED] wrote:
http://www.redhat.com/swr/noarch/autoconf-2.57-3.noarch.html
That's a RedHat 9 RPM, not an Advanced Server 2.1 RPM.
Excuse my RedHat ignorance, but could you explain the difference?
RedHat split
On Wednesday 21 July 2004 14:40, Dossy wrote:
On 2004.07.21, John Caruso [EMAIL PROTECTED] wrote:
http://www.redhat.com/swr/noarch/autoconf-2.57-3.noarch.html
That's a RedHat 9 RPM, not an Advanced Server 2.1 RPM.
Excuse my RedHat ignorance, but could you explain the difference? Will
12 matches
Mail list logo
