From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: links to some info/sources (Heirloom, pcc, ncurses)?
Date: Mon, 18 Jun 2012 18:31:35 +0200 [thread overview]
Message-ID: <20120618163135.GV17860@port70.net> (raw)
In-Reply-To: <CAK8RtFrA0FJBmX1MWQNiP+tvG+X3cQU50FheHqSaVLrbZdpf5w@mail.gmail.com>
* Jens Staal <staal1978@gmail.com> [2012-06-18 17:11:02 +0200]:
> I have seen some messages pass about someone setting up a
> musl-compiled pcc (and pcc-compiled musl) that was able to build
> Heirloom and I just wonder if there is a source for the pcc wrapper
> script used (similar to the musl-gcc one). I am interested in trying
> something similar in AUR (and put it in as an optional compilation
> alternative for the Heirloom packages), but my googling failed to find
> a good source.
>
building with pcc+musl:
http://www.openwall.com/lists/musl/2012/05/16/4
http://www.openwall.com/lists/musl/2012/05/17/4
i built heirloom with pcc+musl but i think the modifications
i used are mostly the same as the heirloom patches in sabotage
but i can dig up my scripts if you want
> 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 managed to build ncurses with musl+pcc using -D_GNU_SOURCE etc
for heirloom i needed minor hacks like
echo '#include <ncurses/curses.h>' >include/curses.h
echo '#include <ncurses/term.h>' >include/term.h
next prev parent reply other threads:[~2012-06-18 16:31 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 [this message]
2012-06-18 16:41 ` Rich Felker
2012-06-19 1:00 ` Isaac Dunham
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=20120618163135.GV17860@port70.net \
--to=nsz@port70.net \
--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).