From: Robin Bowes <robin-lists@robinbowes.com>
To: supervision@list.skarnet.org
Subject: Re: Problems Compiling with glibc 2.12.1
Date: Mon, 13 Jun 2011 18:19:51 +0100 [thread overview]
Message-ID: <4DF646B7.4090608@robinbowes.com> (raw)
In-Reply-To: <20110613133819.GA27014@skarnet.org>
On 06/13/2011 02:38 PM, Laurent Bercot wrote:
>> ./load runit unix.a byte.a -static
>
> My nose is tingling.
>
>
>> Anyone got any ideas how I can get runit built on NexentaStor/OpenSolaris ?
>
> What if you remove the -static from the Makefile ?
> The runit and runit-init binaries are always linked statically, in order
> to avoid runtime libc dependencies; but maybe your gcc doesn't understand
> -static when it's there on the command line, or your system simply does
> not provide a static version of the libc. (Which would suck, but hey,
> it's Solaris-based.)
Removing -static from the Makefile worked. I even added back the "-s" in
src/conf-ld.
I just did this before running package/install:
perl -pi -e 's/-static//' src/Makefile
which removes -static from the following two lines
runit: load runit.o unix.a byte.a
./load runit unix.a byte.a -static
runit-init: load runit-init.o unix.a byte.a
./load runit-init unix.a byte.a -static
So, looks like gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2nexenta7) doesn't like the
-static switch.
R.
--
"Feed that ego and you starve the soul" - Colonel J.D. Wilkes
http://www.theshackshakers.com/
prev parent reply other threads:[~2011-06-13 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 15:29 Mike Buland
2011-02-06 23:12 ` Lasse Kliemann
2011-02-07 0:50 ` Laurent Bercot
2011-02-07 2:09 ` Charlie Brady
2011-02-07 7:56 ` Laurent Bercot
2011-02-08 0:16 ` Lasse Kliemann
2011-06-13 13:01 ` Robin Bowes
2011-06-13 13:38 ` Laurent Bercot
2011-06-13 17:19 ` Robin Bowes [this message]
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=4DF646B7.4090608@robinbowes.com \
--to=robin-lists@robinbowes.com \
--cc=supervision@list.skarnet.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).