From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] about compiling 3.5.1
Date: Tue, 24 Jun 2014 11:11:49 -0700 [thread overview]
Message-ID: <8761jq9nyy.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140524100948.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 24 Jun 2014 10:09:48 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> I don't think it does any harm to list lncurses in LDLIBS,
> and for some it solves a problem; so shall I plop it in?
Yes. This is also needed for the static build.
-- Chris
next prev parent reply other threads:[~2014-06-24 18:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 14:09 Karl Dahlke
2014-06-24 18:11 ` Chris Brannon [this message]
2014-06-25 18:40 ` Adam Thompson
-- strict thread matches above, loose matches on Subject: below --
2014-05-07 22:54 [Edbrowse-dev] jQuery Karl Dahlke
2014-06-21 9:43 ` [Edbrowse-dev] about compiling 3.5.1 Kevin Carhart
2014-06-21 9:58 ` Charles Hallenbeck
2014-06-21 22:15 ` Kevin Carhart
2014-06-21 23:03 ` Chris Brannon
2014-06-22 16:41 ` Adam Thompson
2014-06-22 23:39 ` Kevin Carhart
2014-06-24 14:02 ` Adam Thompson
2014-06-25 1:48 ` Kevin Carhart
2014-06-25 18:34 ` Adam Thompson
2014-06-25 23:44 ` Kevin Carhart
2014-06-26 9:53 ` Kevin Carhart
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=8761jq9nyy.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.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;
as well as URLs for NNTP newsgroup(s).