Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Build on OSX
Date: Tue, 27 Feb 2007 16:57:00 -0000	[thread overview]
Message-ID: <20070227165651.GD31729@caradoc.them.org> (raw)
In-Reply-To: <C61B6EC5-94B9-47F9-95EA-7E2E1358D952@monami-software.com>

On Mon, Feb 12, 2007 at 06:19:26PM +0900, Masaki Muranaka wrote:
> 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.

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.

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

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-02-27 16:57 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 [this message]
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=20070227165651.GD31729@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=monaka@monami-software.com \
    /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