public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jacob Todd <jaketodd422@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to build a static application binary?
Date: Fri, 3 Dec 2010 11:53:11 -0500	[thread overview]
Message-ID: <AANLkTin9gTFUGPtt-ieJ9whLFAGM9tDFMyeXDKaN-8UR@mail.gmail.com> (raw)
In-Reply-To: <idb29v$jsk$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

Iirc there a bug in glibc that makes it almost impossible to create static
binaries with it. I can't look the the sources of that info atm, but it be
easily found with google. Do the other platforms you use gcc to build static
binaries with use a different libc?
On Dec 3, 2010 11:14 AM, "Grant Edwards" <grant.b.edwards@gmail.com> wrote:
> On 2010-12-03, Jacob Todd <jaketodd422@gmail.com> wrote:
>
>> Gotta love gcc!
>
> It's not gcc's fault.
>
> I use gcc on other platforms to create static binaries and don't see
> any noticable overhead.
>
>> If you want real static binaries on a unix-ish os, use plan 9.
>
> Except that's not what I want. I want a static binary on Linux.
>
> --
> Grant Edwards grant.b.edwards Yow! My Aunt MAUREEN was a
> at military advisor to IKE &
> gmail.com TINA TURNER!!
>
>

[-- Attachment #2: Type: text/html, Size: 1285 bytes --]

  reply	other threads:[~2010-12-03 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  1:23 [gentoo-user] How to build a static application binary? Grant Edwards
2010-12-03  4:48 ` Jacob Todd
2010-12-03 15:27   ` [gentoo-user] " Grant Edwards
2010-12-03 16:53     ` Jacob Todd [this message]
2010-12-03 22:32       ` Grant Edwards
     [not found] <fVtfY-2Jt-7@gated-at.bofh.it>
2010-12-03 17:00 ` [gentoo-user] " David W Noon
2010-12-03 22:37   ` [gentoo-user] " Grant Edwards
2010-12-03 23:34     ` Alan McKinnon
2010-12-04  5:25       ` Grant Edwards

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=AANLkTin9gTFUGPtt-ieJ9whLFAGM9tDFMyeXDKaN-8UR@mail.gmail.com \
    --to=jaketodd422@gmail.com \
    --cc=gentoo-user@lists.gentoo.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