From: Masaki Muranaka <monaka@monami-software.com>
To: gdb-patches@sourceware.org
Subject: [RFC] Build on OSX
Date: Mon, 12 Feb 2007 09:19:00 -0000 [thread overview]
Message-ID: <C61B6EC5-94B9-47F9-95EA-7E2E1358D952@monami-software.com> (raw)
Hello,
I've trying to build cross-gdb on OSX host from CVS head.
And the build was failed with following message:
/usr/bin/ld: warning multiple definitions of symbol _locale_charset
./../intl/libintl.a(localcharset.o) definition of _locale_charset in
section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../../libiconv.dylib
(localcharset.o) definition of _locale_charset
It is well known issue. OSX (maybe also Darwin) hosts
need to link 'resolv' library beforge libintl.a.
Here is a brute-forced patch. But I don't think this is
the good solution.
Any comments appreciated.
- - - - - - -
Index: configure.ac
===================================================================
RCS file: /cvs/src/src/gdb/configure.ac,v
retrieving revision 1.42
diff -u -p -r1.42 configure.ac
--- configure.ac 2 Feb 2007 22:54:09 -0000 1.42
+++ configure.ac 12 Feb 2007 08:55:46 -0000
@@ -1591,6 +1591,13 @@ AC_DEFINE(GDB_DEFAULT_HOST_CHARSET, "ISO
AM_ICONV
+# Darwin (MacOSX Tiger) needs -lresolv before libintl.a.
+if test x"$LIBINTL" != x; then
+ case ${host} in
+ *darwin*) LIBINTL="-lresolv $LIBINTL";
+ esac
+fi
+
AC_OUTPUT(Makefile .gdbinit:gdbinit.in,
[
dnl Autoconf doesn't provide a mechanism for modifying definitions
--
Masaki Muranaka
Monami software
next reply other threads:[~2007-02-12 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 9:19 Masaki Muranaka [this message]
2007-02-27 16:57 ` Daniel Jacobowitz
2007-02-28 10:18 ` Masaki Muranaka
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=C61B6EC5-94B9-47F9-95EA-7E2E1358D952@monami-software.com \
--to=monaka@monami-software.com \
--cc=gdb-patches@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