From: Ormund Williams <ormundw@panix.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem linking xlib_libXpm-3.5.12/sxpm
Date: Tue, 02 Jan 2018 22:24:18 -0500 [thread overview]
Message-ID: <1514949858.20163.19.camel@panix.com> (raw)
Hi All,
My host machine died and I had to upgrade, so I went from an x86 32bit
to and AMD 64bit (WOW!!). That required a complete rebuild since the
tool-chain would no longer work due to 32-64 conflicts.
But a seemingly unrelated error cropped up:
CCLD sxpm
sxpm.o: In function `Usage':
sxpm.c:(.text+0x14): undefined reference to `libintl_gettext'
sxpm.c:(.text+0x30): undefined reference to `libintl_gettext'
sxpm.o: In function `ErrorMessage':
sxpm.c:(.text+0x170): undefined reference to `libintl_gettext'
sxpm.c:(.text+0x186): undefined reference to `libintl_gettext'
sxpm.c:(.text+0x1ba): undefined reference to `libintl_gettext'
sxpm.o:sxpm.c:(.text+0x1d0): more undefined references to `libintl_gettext' follow
sxpm.o: In function `main':
sxpm.c:(.text.startup+0x3a): undefined reference to `libintl_bindtextdomain'
sxpm.c:(.text.startup+0x46): undefined reference to `libintl_textdomain'
sxpm.c:(.text.startup+0x81): undefined reference to `libintl_gettext'
sxpm.c:(.text.startup+0xa17): undefined reference to `libintl_gettext'
collect2: error: ld returned 1 exit status
Makefile:417: recipe for target 'sxpm' failed
I don't need libXaw (Athena Widgets) so I disabled it but the error
again pops up when samba starts linking:
[3246/3801] Linking default/lib/util/libutil-tdb-samba4.so
default/source4/heimdal/lib/com_err/error_126.o: In function `com_right_r':
error.c:(.text+0x85): undefined reference to `libintl_dgettext'
Some research into this error points to an "incorrect sequence of
CCFLAGS or LDFLAGS", help?
__
Ormund
next reply other threads:[~2018-01-03 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 3:24 Ormund Williams [this message]
2018-01-03 10:17 ` [Buildroot] Problem linking xlib_libXpm-3.5.12/sxpm Thomas Petazzoni
2018-01-03 11:37 ` Ormund Williams
2018-01-03 12:06 ` Ormund Williams
2018-01-03 13:35 ` Thomas Petazzoni
2018-01-03 22:23 ` Thomas Petazzoni
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=1514949858.20163.19.camel@panix.com \
--to=ormundw@panix.com \
--cc=buildroot@busybox.net \
/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