Date: Thu, 9 Jun 2016 01:09:32 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, Gerald Pfeifer <gerald@pfeifer.com>, Andreas Tobler <andreast@FreeBSD.org>, Baptiste Daroussin <bapt@FreeBSD.org>, Tijl Coosemans <tijl@freebsd.org> Subject: Re: Duplicate OPT_ entries in gcc/options.h Message-ID: <823B7E6C-4B47-401F-A254-C88825AE5562@FreeBSD.org> In-Reply-To: <ff093e89-7ccc-6bc6-1897-e7a04ae39f57@FreeBSD.org> References: <alpine.LSU.2.20.1606082038000.2798@anthias.pfeifer.com> <75411813-0C9B-4CEF-BEE4-8B26DD8346F7@FreeBSD.org> <0610816e-2675-1abf-a4ee-274807317932@FreeBSD.org> <5A8D0A1F-6EA3-4DF2-82A2-EC1309C33E1E@FreeBSD.org> <ff093e89-7ccc-6bc6-1897-e7a04ae39f57@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 09 Jun 2016, at 00:30, Jung-uk Kim <jkim@FreeBSD.org> wrote: > > On 06/ 8/16 06:16 PM, Dimitry Andric wrote: >> On 08 Jun 2016, at 23:54, Jung-uk Kim <jkim@FreeBSD.org> wrote: >>> >>> On 06/ 8/16 05:15 PM, Dimitry Andric wrote: >>>> On 08 Jun 2016, at 21:11, Gerald Pfeifer <gerald@pfeifer.com> wrote: >>>>> >>>>> I got a user report, and could reproduce this, that building >>>>> GCC (lang/gcc, but also current HEAD, so probably pretty much >>>>> any version) with FreeBSD 11 and LANG = en_US.UTF-8 we get >>>>> conflicting entires in $BUILDDIR/gcc/options.h such as >> ... >>>> Note that GNU awk does *not* produce a different optionlist file when >>>> used with either LANG=C or LANG=en_US.UTF-8. >> ... >>>> So I am assuming that the ARRAY[j-1] > ARRAY[j] comparison works >>>> differently in our awk, depending on the LANG settings. No idea when >>>> that changed, though, if it changed at all... >>> >>> This behaviour is known for very long time: >>> >>> https://svnweb.freebsd.org/changeset/base/173731 >>> >>> and it is not our fault: >>> >>> https://www.gnu.org/software/gawk/manual/html_node/POSIX-String-Comparison.html >> >> >> Indeed, so the real question is: why does this only started coming up >> now, if it is known since 2007? I have been building gcc ports for >> ages, and never ran into this problem, but I also have never actively >> used a persistent LANG environment variable, let alone with UTF-8 in it. >> >> Is this because more people started using UTF-8 recently? > > We are doing more correct collation now: > > https://svnweb.freebsd.org/changeset/base/290494 Indeed. This problem has come up before on the ports mailing list, almost immediately after that commit: https://lists.freebsd.org/pipermail/freebsd-ports/2015-November/101034.html Apparently some proposals were made to set LANG and LC_ALL to C globally for port builds, but it was never implemented? I guess more people are now noticing it, because they are trying out the 11.0-ALPHA installers. -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAldYpbMACgkQsF6jCi4glqOvRwCg7FP7GcUrJuQisQeu8n++tTlp JhkAnjadknX5jP5TucYDY3BSCbvOoMIc =N6bR -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?823B7E6C-4B47-401F-A254-C88825AE5562>