Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Masaki Muranaka <monaka@monami-software.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Build on OSX
Date: Wed, 28 Feb 2007 10:18:00 -0000	[thread overview]
Message-ID: <5C32E705-6B6E-4CD9-9A84-547E5816DDBE@monami-software.com> (raw)
In-Reply-To: <20070227165651.GD31729@caradoc.them.org>


On 2007/02/28, at 1:56, Daniel Jacobowitz wrote:
>> /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.
>
> I know that people built GCC on this platform all the time.  GCC
> doesn't explicitly do this, so why does it work for GCC but not for
> GDB?  I would recommend building GCC and trying to figure out what's
> different.

I have an mistake. In fact, there is warning already shown, but
binaries (gdb, gdbtui) are generated successfully.

> (You can build just a C compiler with --enable-languages=c, that's
> much quicker.)

I can't build GCC immediately because I don't have darwin version of
GMP/MPFR. So I'm not sure, but it is posible that GCC developers
regard this issue as harmless.

--
Masaki Muranaka
Monami software



      reply	other threads:[~2007-02-28 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12  9:19 Masaki Muranaka
2007-02-27 16:57 ` Daniel Jacobowitz
2007-02-28 10:18   ` Masaki Muranaka [this message]

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=5C32E705-6B6E-4CD9-9A84-547E5816DDBE@monami-software.com \
    --to=monaka@monami-software.com \
    --cc=drow@false.org \
    --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