Summary: | net-dns/dnsmasq-2.60 - x86_64-pc-linux-gnu-gcc: en_GB: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Neil Bothwick <neil> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | jer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
environment file, as requested |
Description
Neil Bothwick
2012-03-10 09:00:49 UTC
* The ebuild environment file is located at '/var/tmp/portage/net-dns/dnsmasq-2.60/temp/environment'. Please attach that. Created attachment 305175 [details]
environment file, as requested
(In reply to comment #2) > Created attachment 305175 [details] > environment file, as requested From your environment: declare -x i18n="en_GB" The top level Makefile sets this: ./Makefile: i18n=-DLOCALEDIR=\'\"$(LOCALEDIR)\"\' \ which is then used in: .c.o: $(CC) $(CFLAGS) $(COPTS) $(i18n) $(build_cflags) $(RPM_OPT_FLAGS) -c $< Can you check whether i18n=en_GB is set in the environment of the shell that runs emerge, please? Yes it is, in /etc/env.d/02locale, a file that has not been modified since July 2009. Removing it allows the package to emerge successfully. (In reply to comment #4) > Yes it is, in /etc/env.d/02locale, a file that has not been modified since > July 2009. Removing it allows the package to emerge successfully. Can you check what package owns that file? I actually have *one* system that has the file, but it's been there even longer and its contents differ: epia ~ # ls -l /etc/env.d/02locale -rw-r--r-- 1 root root 21 Aug 9 2005 /etc/env.d/02locale epia ~ # cat /etc/env.d/02locale LC_ALL="en_US.UTF-8" Let's say it's safe to remove and get on with it. :) No package own it, I created to get round some locale issues at some time. It comes up on the lists and forums from time to time and may even be mentioned in the docs somewhere, but 2009 was a long time ago. It's odd that this particular release of dnsmasq has the problem when nothing else does (I have the same file on all my boxes). |