From: carbonated beverage <ramune@net-ronin.org>
To: linux-kernel@vger.kernel.org
Subject: build breakage scripts/kconfig/conf
Date: Tue, 7 Feb 2006 21:13:57 -0800 [thread overview]
Message-ID: <20060208051357.GA32025@prophet.net-ronin.org> (raw)
barbeque/zarathustra:linux-2.6: SHELL=/bin/bash make oldconfig
HOSTLD scripts/kconfig/conf
/usr/bin/ld: cannot find -lintl
collect2: ld returned 1 exit status
make[1]: *** [scripts/kconfig/conf] Error 1
make: *** [oldconfig] Error 2
by:
5e375bc7d586e0df971734a5a5f1f080ffd89b68
[PATCH] kconfig: detect if -lintl is needed when linking conf,mconf
KBUILD_NEED_LINTL := $(shell \
if echo -e "\#include <libintl.h>\nint main(int a, char** b) { gettext(\"\"); return 0; }\n" | \
$(HOSTCC) $(HOSTCFLAGS) -x c - -o /dev/null> /dev/null 2>&1 ; \
then echo no ; \
else echo yes ; fi)
ifeq ($(KBUILD_NEED_LINTL),yes)
HOSTLOADLIBES_conf += -lintl
HOSTLOADLIBES_mconf += -lintl
endif
Running the commands manually, it returns the correct values.
Running it via make, it pukes.
Tried adding SHELL=/bin/bash to the Makefile fragment, and also tried:
SHELL=/bin/bash
KBUILD_NEED_LINTL := $(shell \
bash -c 'if echo -e "\#include <libintl.h>\nint main(int a, char** b) { gettext(\"\") ; return 0; }\n" | \
$(HOSTCC) $(HOSTCFLAGS) -x c - -o /dev/null> /dev/null 2>&1 ; \
then echo no ; \
else echo yes ; fi')
ifeq ($(KBUILD_NEED_LINTL),yes)
HOSTLOADLIBES_conf += -lintl
HOSTLOADLIBES_mconf += -lintl
endif
foo:
echo ${HOSTLOADLIBES_mconf}
echo ${HOSTLOADLIBES_conf}
Still bombs out.
However:
barbeque/zarathustra:linux-2.6: if echo -e '#include <libintl.h>
int main(int a, char** b)
{
gettext("");
return 0;
}
' | cc -x c - -o /dev/null > /dev/null 2>&1 ; then
> echo no
> else
> echo yes
> fi
no
So... anyone have an idea what's going on?
The shell output was under bash, with SHELL set to /bin/bash.
Debian amd64 port, using the stable tree:
barbeque/zarathustra:linux-2.6: make --version|head -1 ; gcc --version|head -1
GNU Make 3.80
gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
-- DN
Daniel
reply other threads:[~2006-02-08 5:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060208051357.GA32025@prophet.net-ronin.org \
--to=ramune@net-ronin.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®