From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: links to some info/sources (Heirloom, pcc, ncurses)?
Date: Mon, 18 Jun 2012 18:00:27 -0700 [thread overview]
Message-ID: <20120618180027.57746bf7@newbook> (raw)
In-Reply-To: <20120618164136.GE163@brightrain.aerifal.cx>
On Mon, 18 Jun 2012 12:41:36 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> On Mon, Jun 18, 2012 at 06:31:35PM +0200, Szabolcs Nagy wrote:
> > > The second question was regarding ncurses. Some utilities in
> > > Heirloom require curses but I fail to build it for musl - but it
> > > seems to be in Sabotage. Are there any good patches/tricks around
> > > to get it to build?
I used this patch (not sure if still needed):
===
diff -ur ncurses-5.9/ncurses/SigAction.h
ncurses-5.9-d/ncurses/SigAction.h ---
ncurses-5.9/ncurses/SigAction.h 2005-08-06 13:05:32.000000000
-0700 +++ ncurses-5.9-d/ncurses/SigAction.h 2012-04-03
16:32:56.841630774 -0700 @@ -49,6 +49,8 @@ #define HAVE_SIGVEC 0
#endif
+#include <signal.h>
+
#if HAVE_SIGACTION
#if !HAVE_TYPE_SIGACTION
===
and these configure options:
CC=musl-gcc CFLAGS="-fno-stack-protector -Os -D_GNU_SOURCE" ./configure
--prefix=${PREFIX} --without-cxx --with-fallbacks=xterm
#forgot to add --enable-widec
(see github.com/idunham/src-musl if you'd like to see my full build
scripts...really, it ended up looking a lot like a pkgbuild, but
somewhat more awkward)
> Indeed, it's worked for a long time, but you need to disable the C++
> interfaces if you don't have a working C++ toolchain. I don't think
> the configure script does this by default. Actually ncurses has A LOT
> of broken options by default which you need to fix when running
> configure; for instance, it does not support UTF-8 unless you use
> --enable-wide or something like that.
I've always used CXX=false for stuff like this...
The --enable-wide is because for some reason, using wchar_t instead of
char breaks the ABI.
> > for heirloom i needed minor hacks like
> >
> > echo '#include <ncurses/curses.h>' >include/curses.h
> > echo '#include <ncurses/term.h>' >include/term.h
AKA:
CPPFLAGS += -I${sysincdir}/ncurses
CFLAGS += ${CPPFLAGS} # if the makefile ignores CPPFLAGS
> This is another issue: the installation paths and filenames. I don't
> know the right option to make ncurses install itself as the default
> curses library...
It doesn't seem to allow installing $sysincdir/curses.h
FYI: pdcurses may also be an option.
Isaac Dunham
next prev parent reply other threads:[~2012-06-19 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 15:11 Jens Staal
2012-06-18 16:06 ` John Spencer
2012-06-18 16:31 ` Szabolcs Nagy
2012-06-18 16:41 ` Rich Felker
2012-06-19 1:00 ` Isaac Dunham [this message]
2012-06-19 1:08 ` Rich Felker
2012-06-19 1:47 ` Isaac Dunham
2012-06-19 5:58 ` Jens Staal
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=20120618180027.57746bf7@newbook \
--to=idunham@lavabit.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).