Jeff Trawick wrote:
>
> Jim Jagielski <[EMAIL PROTECTED]> writes:
>
> > Yep... Looks like it's no problem with 2.52.
> >
> > Anyone have hearburn if I adjust buildcheck.sh to make 2.52 the
> > new requirement?
>
> at least a little, but I'm not exactly sure how much :) In the 2.0.30
> timeframe
Jim Jagielski <[EMAIL PROTECTED]> writes:
> Yep... Looks like it's no problem with 2.52.
>
> Anyone have hearburn if I adjust buildcheck.sh to make 2.52 the
> new requirement?
at least a little, but I'm not exactly sure how much :) In the 2.0.30
timeframe a colleage was unable to get "make dis
Justin Erenkrantz wrote:
>
> IIRC, FreeBSD's ports package doesn't include anything beyond 2.13.
> So, this will cause problems if we roll on icarus. If I get a
> chance, I'll try it with autoconf-2.13 here later on Solaris and see
> if I can figure out what is going on.
>
I'll take a look as w
On Wed, Mar 06, 2002 at 04:08:14PM -0500, Jim Jagielski wrote:
> Yep... Looks like it's no problem with 2.52.
>
> Anyone have hearburn if I adjust buildcheck.sh to make 2.52 the
> new requirement?
IIRC, FreeBSD's ports package doesn't include anything beyond 2.13.
So, this will cause problems if
On Wed, 6 Mar 2002, Jim Jagielski wrote:
> Yep... Looks like it's no problem with 2.52.
>
> Anyone have hearburn if I adjust buildcheck.sh to make 2.52 the
> new requirement?
IIRC 2.52 still produces a non-portable case..esac statement
which fails on FreeBSD.
If this issue happens wi
Yep... Looks like it's no problem with 2.52.
Anyone have hearburn if I adjust buildcheck.sh to make 2.52 the
new requirement?
Jim Jagielski wrote:
>
> I'll adjust PATH and see if that's the dependency... It's not libtool
> dependent AFAIK (I tried 1.4.2 and 1.3.5).
>
> Justin Erenkrantz wrote:
Anyone else seeing problems getting ./configure to work at all
with autoconf's cache-file under Solaris? Unless I specify the cache-file,
configure will die. That is:
./configure --cache-file=/tmp/my.cache
or
./configure --cache-file=/dev/null
will work, but without the
