On 2010-01-03 15:03, Jilles Tjoelker wrote:
This should be fixed by adding LC_ALL=C somewhere in the build process,
possibly only for these awk commands.
Here is a quite minimal diff to do so, at least for the buildkernel
part.
In any case, it looks like awk is used quite a lot in other places
during buildworld; some of these invocations already use LC_ALL=C, most
of them do not. There are even invocations of sh using LC_ALL=C. :)
Instead of peppering the whole tree with LC_ALL=C insertions, would it
make sense to simply set LC_ALL=C globally during building world and
kernel? Or are there parts that actually use locales during the build?
Index: sys/conf/kern.pre.mk
===================================================================
--- sys/conf/kern.pre.mk (revision 201193)
+++ sys/conf/kern.pre.mk (working copy)
@@ -14,7 +14,7 @@
M= ${MACHINE_ARCH}
-AWK?= awk
+AWK?= LC_ALL=C awk
LINT?= lint
NM?= nm
OBJCOPY?= objcopy
Index: sys/conf/kmod.mk
===================================================================
--- sys/conf/kmod.mk (revision 201193)
+++ sys/conf/kmod.mk (working copy)
@@ -60,7 +60,7 @@
# Unload a module.
#
-AWK?= awk
+AWK?= LC_ALL=C awk
KMODLOAD?= /sbin/kldload
KMODUNLOAD?= /sbin/kldunload
OBJCOPY?= objcopy
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
