[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] autoconfiscation

From: Rob Landley
Subject: Re: [Tinycc-devel] autoconfiscation
Date: Thu, 30 Aug 2007 17:49:31 -0500
User-agent: KMail/1.9.6

On Thursday 30 August 2007 1:40:44 am Simon 'corecode' Schubert wrote:
> Rob Landley wrote:
> > The reason you can't run a glibc version of gcc against uClibc is that
> > pieces of gcc like libgcc_s.so link against their libc, and leak
> > references to that libc.  So if you ever divide by a 64 bit number on a
> > 32 bit platform or weird corner cases like that, a reference to glibc
> > sneaks into your uClibc program. Since libgcc is part of the gcc source
> > code, the only way to build a version of that library which leaks a
> > reference the _right_ libc is to rebuild gcc against uClibc, from source
> > code.
> This is just because libgcc is dynamically linked.  You can change that,
> only producing a static version, which in turn never introduces references
> to  a specific libc.  Don't ask me how to do that officially, because my
> setup uses completely different makefiles alltogether.

--disable-shared in config.  I'm doing that in firmware linux.

But the versions of gcc that come with Fedora and Ubuntu and such don't do 
that, and to make it do that you have to rebuild gcc from source...

"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]