On Wed, 8 Jun 2016 19:21:16 -0400 Jung-uk Kim <j...@freebsd.org> wrote: > On 06/ 8/16 07:09 PM, Dimitry Andric wrote: >> On 09 Jun 2016, at 00:30, Jung-uk Kim <j...@freebsd.org> wrote: >>> On 06/ 8/16 06:16 PM, Dimitry Andric wrote: >>>> On 08 Jun 2016, at 23:54, Jung-uk Kim <j...@freebsd.org> wrote: >>>>> On 06/ 8/16 05:15 PM, Dimitry Andric wrote: >>>>>> On 08 Jun 2016, at 21:11, Gerald Pfeifer <ger...@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? > > tijl proposed it but never implemented because of difficulties to > exp-run the change, it seems. > > http://docs.freebsd.org/cgi/mid.cgi?20151127145552.GA19655
There are over 300 files in the ports tree that match "[[:<:]]LANG[[:>:]]". I just don't have the time to go over all of them. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
