From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Re: libiberty
Date: Sun, 03 Jan 2010 23:26:00 -0000 [thread overview]
Message-ID: <2bf229d31001031526n17bb122q5554a0c29b0523a@mail.gmail.com> (raw)
In-Reply-To: <20100103224555.GA17181@caradoc.them.org>
>> I'm building gdb for MinGW and I was wondering if gdb needs to use
>> it's own libiberty? If not, is it possible to link against the
>> libiberty included as part of binutils? How would I go about doing so
>> assuming it is possible?
>
> Generally GDB needs to use its own copy. Applications using libiberty
> always include their own copy for this reason.
Fair enough, is there a way to add a prefix specifically to gdb's
libiberty (i.e. instead of installing to lib32/libiberty.a install to
lib32/gdb/libiberty.a), or perhaps add a suffix (like libiberty.gdb.a)
so as to not cause a conflict with binutils' libiberty?
Thank you,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
next prev parent reply other threads:[~2010-01-03 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 22:21 libiberty Chris Sutcliffe
2010-01-03 22:46 ` libiberty Daniel Jacobowitz
2010-01-03 23:26 ` Chris Sutcliffe [this message]
2010-01-04 0:04 ` libiberty 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=2bf229d31001031526n17bb122q5554a0c29b0523a@mail.gmail.com \
--to=ir0nh34d@gmail.com \
--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