[Bug 216124] Mk/bsd.port.mk: set LC_COLLATE=C for CONFIGURE_ENV and MAKE_ENV
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Jan 15 21:20:27 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216124
Bug ID: 216124
Summary: Mk/bsd.port.mk: set LC_COLLATE=C for CONFIGURE_ENV and
MAKE_ENV
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Ports Framework
Assignee: portmgr at FreeBSD.org
Reporter: gerald at FreeBSD.org
CC: andreast at FreeBSD.org, dim at FreeBSD.org,
freebsd-ports-bugs at FreeBSD.org, jkim at FreeBSD.org,
portmgr at FreeBSD.org
Attachment #178935 maintainer-approval?(portmgr at FreeBSD.org)
Flags:
CC: portmgr at FreeBSD.org
Created attachment 178935
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178935&action=edit
Proposed patch to set LC_COLLATE in CONFIGURE_ENV and MAKE_ENV
Starting with FreeBSD 11, awk follows "natural", but unexpected (to many
of us and existing programs) sorting and string comparisons when used in
a locale different than the C locale.
This hit us when building GCC under the new version, cf.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210122
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211742
It quite likely is going to hit us in many other cases, not the least
since the behavior of GNU awk matches the original FreeBSD awk behavior
(unless POSIXLY_CORRECT is set in the environment).
So, and as a general best practice to increase reproducability, let's
set LC_COLLATE=C when building ports and packages per the attached.
I verified this fixes building the lang/gcc* ports when the current
workaround is removed.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-ports-bugs
mailing list