edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] about compiling 3.5.1
Date: Wed, 25 Jun 2014 19:40:39 +0100	[thread overview]
Message-ID: <20140625184039.GE5577@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <8761jq9nyy.fsf@mushroom.PK5001Z>

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

On Tue, Jun 24, 2014 at 11:11:49AM -0700, Chris Brannon wrote:
> 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.

Certainly. As you say, it appears to be harmless and fixes things for some 
people.
I'm interested to know why this is needed on some systems and not on others.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-06-25 18:41 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
2014-06-25 18:40   ` Adam Thompson [this message]
  -- 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=20140625184039.GE5577@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chris@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).