From: Michael Peters <djchord@me.com>
To: crossgcc@sourceware.org
Subject: ct-ng build fails on MacOS X using KBUILD_NO_NLS=1
Date: Tue, 08 May 2012 18:15:00 -0000 [thread overview]
Message-ID: <5C5F4A6D-3233-4D78-99B3-486FFBA3C89F@me.com> (raw)
Hi all,
I'm trying to get a cross compiler going on my mac here and seem to be having a bad time of it. I note the mac having problems with localization is a known issue, but when I use the KBUILD_NO_NLS=1 variable to make ct-ng, it seems to be getting ignored. Below is the output I get:
assylum:crosstool-ng-1.15.0$ KBUILD_NO_NLS=1 make
SED 'ct-ng'
SED 'scripts/crosstool-NG.sh'
SED 'scripts/saveSample.sh'
SED 'scripts/showTuple.sh'
GEN 'config/configure.in'
GEN 'paths.mk'
GEN 'paths.sh'
DEP 'nconf.gui.dep'
DEP 'nconf.dep'
DEP 'lxdialog/yesno.dep'
DEP 'lxdialog/util.dep'
DEP 'lxdialog/textbox.dep'
DEP 'lxdialog/menubox.dep'
DEP 'lxdialog/inputbox.dep'
DEP 'lxdialog/checklist.dep'
DEP 'mconf.dep'
DEP 'conf.dep'
BISON 'zconf.tab.c'
GPERF 'zconf.hash.c'
LEX 'lex.zconf.c'
DEP 'zconf.tab.dep'
CC 'zconf.tab.o'
CC 'conf.o'
LD 'conf'
Undefined symbols for architecture x86_64:
"_libintl_gettext", referenced from:
_conf_parse in zconf.tab.o
_conf_read_simple in zconf.tab.o
_conf_write in zconf.tab.o
_get_prompt_str in zconf.tab.o
_get_symbol_str in zconf.tab.o
_get_relations_str in zconf.tab.o
_menu_get_ext_help in zconf.tab.o
...
"_libintl_setlocale", referenced from:
_main in conf.o
"_libintl_bindtextdomain", referenced from:
_main in conf.o
"_libintl_textdomain", referenced from:
_main in conf.o
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit status
make[2]: *** [conf] Error 1
make[1]: *** [build-lib-kconfig] Error 2
make: *** [build] Error 2
Any advice would be appreciated, thanks!
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2012-05-08 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 18:15 Michael Peters [this message]
2012-05-08 19:55 ` Yann E. MORIN
2012-05-08 22:29 ` Michael Peters
2012-08-01 11:42 ` Samuel Martin
2012-08-01 11:47 ` Yann E. MORIN
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=5C5F4A6D-3233-4D78-99B3-486FFBA3C89F@me.com \
--to=djchord@me.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).