public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/17077] --with-system-readline uses bundled readline include files
Date: Fri, 20 Jun 2014 21:11:00 -0000 [thread overview]
Message-ID: <bug-17077-4717-PDyXFHuJLf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17077-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17077
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jan.kratochvil at redhat dot com
--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
(In reply to Samuel Bronson from comment #1)
> But, uh, what's the point of using --with-system-readline if you're linking
> it statically, anyway?
Fedora links libreadline dynamically. Comment 0 says libreadline.a just for
simplicity, I did not mean specifically the .a variant, .so is also OK.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-20 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 10:39 [Bug build/17077] New: " jan.kratochvil at redhat dot com
2014-06-20 18:55 ` [Bug build/17077] " naesten at gmail dot com
2014-06-20 21:11 ` jan.kratochvil at redhat dot com [this message]
2015-07-07 10:58 ` dilyan.palauzov at aegee dot org
2015-07-07 11:41 ` jan.kratochvil at redhat dot com
2015-07-07 11:43 ` jan.kratochvil at redhat dot com
2015-07-13 7:23 ` dilyan.palauzov at aegee dot org
2015-07-13 7:49 ` jan.kratochvil at redhat dot com
2015-07-28 8:49 ` dilyan.palauzov at aegee dot org
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=bug-17077-4717-PDyXFHuJLf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).