On Fri, Nov 27, 2015 at 03:47:21PM +0100, Dimitry Andric wrote:
> On 27 Nov 2015, at 15:41, Steve Wills <swi...@freebsd.org> wrote:
> On 11/27/2015 08:42, Baptiste Daroussin wrote:
> >> On Fri, Nov 27, 2015 at 02:24:05PM +0100, Tijl Coosemans wrote:
> ...
>
> >>> so I was thinking of adding something like this to
> >>> bsd.port.mk:
> >>>
> >>> USE_LOCALE?= C
> >>> LANG= ${USE_LOCALE}
> >>> LC_ALL= ${USE_LOCALE}
> >>> .export LANG LC_ALL
> >>>
> >>> This gives a consistent locale environment for port builds. Some ports
> >>> already set LANG or LC_ALL. That would have to be reviewed and I haven't
> >>> had time for that yet.
> >>
> >> yeah we should imho to that. The same issue appears with GNU tr which also
> >> do not take in account collation (IIRC) while ours do.
> >
> > FWIW, I ran into this building devel/arm-none-eabi-gcc too. Setting
> > LC_ALL and LANG fixed it for me. Also, Mk/bsd.ruby.mk got something
> > similar for gem builds a while ago, though it uses en_US.UTF-8 for
> > LC_ALL and LC_CTYPE=UTF-8. As I recall, this was due to difference in
> > generated docs based on language. We may want to remove the bits from
> > Mk/bsd.ruby.mk if we add it globally. Also, I wonder what impacts this
> > will have beyond fixing builds, such as docs, plist differences or baked
> > in defaults, etc.
>
> This really sounds like it needs an exp-run. :-)An exp-run is really not needed here (will be issued anyway) given when doing exp-run, the locale is the default aka C. and an exp-run was made before importing that code. Bapt
signature.asc
Description: PGP signature
