From: "Matias A. Fonzo" <selk@dragora.org>
To: dash@vger.kernel.org
Subject: --with-libedit errors
Date: Mon, 21 Nov 2016 20:36:43 -0300 [thread overview]
Message-ID: <20161121203643.68a26b1a@rafaela> (raw)
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
Hi there,
I was trying to compile dash against libedit under a native musl-based
environment, using --with-libedit. In the first instance, I was getting
this error:
http://sprunge.us/BKWK
I solved this issue adding #include <getopt.h> (suggested by Laurent
Bercot) to the file src/histedit.c -- as my patch shows at:
http://dragora.org/repo.fsl/artifact/068a14902e390487
Next, I've started receiving this error messages:
http://sprunge.us/iQjf
To sort out this problem I've removed the option --with-libedit, using
LIBS=-ledit for the ./configure invocation. "ldd" reports:
libedit.so.0 => /lib/libedit.so.0 (0x7f2db97a3000)
and
libncursesw.so.6 => /lib/libncursesw.so.6 (0x7f2db954e000)
Right now I have a working dash compiled with libedit support. :-)
Also, my default LDFLAGS has the value "-s" to strip all the symbols,
but dash/configure does not seem to pick up the value...
[-- Attachment #2: Firma digital OpenPGP --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
reply other threads:[~2016-11-21 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161121203643.68a26b1a@rafaela \
--to=selk@dragora.org \
--cc=dash@vger.kernel.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 NNTP newsgroup(s).