From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: shared musl with PCC as system compiler
Date: Sun, 14 Oct 2012 13:36:04 -0700 [thread overview]
Message-ID: <20121014133604.ab52b550.idunham@lavabit.com> (raw)
In-Reply-To: <507AC05C.1060002@gentoo.org>
On Sun, 14 Oct 2012 15:38:36 +0200
Luca Barbato <lu_zero@gentoo.org> wrote:
> On 10/14/2012 09:15 AM, Isaac Dunham wrote:
> > This is mainly a mix of what I've worked out previously and what Rich and I worked
> > out on IRC. I figured posting it on the list would help those who want to use pcc
> > as compiler...
> > 0. Get today's (Oct 13) git HEAD or later! Otherwise libc.so will be broken.
> > Get a fairly recent pcc from CVS (the last month should be good enough)
> > When compiling pcc-libs, use
> > make CFLAGS="-fPIC ${OPTFLAGS}"
> > (otherwise you get textrels in libc.so, which doesn't work)
> > 1. Set LIBCC to -L$(dirname `pcc -print-file-name=libpcc.a`) -lpcc
Or $(${CC} -print-file-name=libpcc.a), as Rich mentioned.
> > 2. Add
> > CFLAGS_ALL_SHARED += -D__PIC__=1
> > to config.mak (pcc doesn't define this with -fPIC at present, which is a bug)
No longer necessary, with today's CVS (DATESTAMP=20121014).
(Additionally, array arguments passed to inline asm _should_ properly decay to pointers now).
> Do you have/know of a git mirror for pcc?
Not until a few minutes ago. ;)
See
git://github.com/idunham/pcc
and
git://github.com/idunham/pcc-libs
(they are not recommended for use unless you need to use git, as I may not keep them current all the time!)
--
Isaac Dunham <idunham@lavabit.com>
next prev parent reply other threads:[~2012-10-14 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 7:15 Isaac Dunham
2012-10-14 13:38 ` Luca Barbato
2012-10-14 20:36 ` Isaac Dunham [this message]
2012-10-14 15:29 ` Rich Felker
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=20121014133604.ab52b550.idunham@lavabit.com \
--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).