--Signature=_Fri__16_Apr_2004_20_12_04_+0200_SKeAsWlbBrWXwFAm
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

On Fri, 16 Apr 2004 11:05:40 -0700 (PDT)
"Jeremy C. Reed" <reed@reedmedia.net> wrote:

> I still get a very long wait for "checking the maximum length of command
> line arguments..." when building libtool-base-1.5.2nb5 under FreeBSD.
> 
> defs.FreeBSD.mk has:
> 
> +# check for maximum command line length and set it in configure's
> environment,
> +# to avoid a test required by the libtool script that takes forever.
> +.if defined(GNU_CONFIGURE) && defined(USE_LIBTOOL)
> +_OPSYS_MAX_CMDLEN!=    /sbin/sysctl -n kern.argmax
> +CONFIGURE_ENV+=                lt_cv_sys_max_cmd_len=${_OPSYS_MAX_CMDLEN}
> 
> Should that CONFIGURE_ENV be used in other situations, like building
> libtool-base?

Errm, ignore my previous mail... I was too fast ! :) I think we should set it
when using libtool or not.

Because there are some packages that doesn't require libtool, so the value is
not  cached.

-- 
	Juan RP <juan@xtraeme.unixbsd.org>

--Signature=_Fri__16_Apr_2004_20_12_04_+0200_SKeAsWlbBrWXwFAm
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAgCH0ypkLYVDran0RAop8AJwKqyrixAciESSBeVnqnEJOfOLGSgCgu+CB
Ss+w1AaYWb+gCTpsy/Zvuq4=
=xrn8
-----END PGP SIGNATURE-----

--Signature=_Fri__16_Apr_2004_20_12_04_+0200_SKeAsWlbBrWXwFAm--