>Number:         9813
>Category:       pkg
>Synopsis:       devel/autoconf finds wrong m4
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 06 17:33:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Robby Griffin
>Release:        NetBSD-1.4.2
>Organization:
TERC
>Environment:
NetBSD khwarizmi 1.4.2 NetBSD 1.4.2 (GENERIC) #3: Wed Mar 15 23:41:54 PST 2000     toddpw@vader.toddpw.net:/usr/src/sys/arch/i386/compile/GENERIC i386

>Description:
In yesterday's -current pkgsrc tarball, building devel/autoconf fails
when it finds /usr/bin/m4 instead of /usr/pkg/bin/gm4 which will have
just been installed via dependency. Autoconf's configure script stops
with an error, complaining that it wants GNU m4 1.1 or later.

devel/autoconf/Makefile tries to force autoconf's configure script to
find /usr/pkg/bin/gm4 by adding it to the CONFIGURE_ENV. But then the
Makefile includes ../../mk/bsd.pkg.mk, which appends a different M4
setting to CONFIGURE_ENV.

>How-To-Repeat:
cd devel/autoconf; make

>Fix:
setenv M4 /usr/pkg/bin/gm4 seemed like a reasonable workaround at
the time.
have the pkg Makefile for autoconf set M4 instead of CONFIGURE_ENV?
have the pkg Makefile include bsd.pkg.mk first, and then override
stuff?
have bsd.pkg.mk prepend rather than append?
have bsd.pkg.mk check for duplicate definitions in CONFIGURE_ENV?
more possibilities exist. someone who cares about the pkg system
should pick one.

>Release-Note:
>Audit-Trail:
>Unformatted: