From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb@sourceware.org, binutils@sourceware.org
Subject: libintl breakage
Date: Tue, 04 Jul 2006 20:16:00 -0000 [thread overview]
Message-ID: <200607042016.k64KGTIY011211@elgar.sibelius.xs4all.nl> (raw)
Currently libbfd fails to build on OpenBSD systems:
gcc -DHAVE_CONFIG_H -I. -I../../../src/gdb/bfd -I. -DNETBSD_CORE -I. -I../../../src/gdb/bfd -I../../../src/gdb/bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c ../../../src/gdb/bfd/archive.c -o archive.o
In file included from ../../../src/gdb/bfd/archive.c:133:
../../../src/gdb/bfd/sysdep.h:172: libintl.h: No such file or directory
The problem here seems to be that the system has the gettext packages
installed in /usr/local, but the system compiler doesn't search
/usr/local by default.
Now for some reason the configure script uses -I/usr/local/include and
-L/usr/local/include, so it finds the installed libintl and decides
not to build the bundled gettext in intl/. However when compiling
bfd/ (and presumably other subdirectories) these options are omitted.
Somehow the logic in gettext-sister.m5, gettext.m4 and/or
lib-prefix.m4 seems to be flawed.
A way around this is to configure with --prefix set to something
that's not /usr/local. Then the bundled intl is built. Unfortunately
it always gets rebuilt, since stamp-h1 is never created.
All in all, it seems that the recent changes to use the new gettext
were never properly tested :(.
Mark
next reply other threads:[~2006-07-04 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 20:16 Mark Kettenis [this message]
2006-07-05 12:48 ` Daniel Jacobowitz
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=200607042016.k64KGTIY011211@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=binutils@sourceware.org \
--cc=gdb@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