|
Home > Archive > Debian Developers > April 2004 > glibc cross-compile
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
glibc cross-compile
|
|
| Albert Cahalan 2004-04-28, 11:33 pm |
| On Tue, 2004-04-27 at 19:09, Benjamin Herrenschmidt wrote:
> (glibc cannot easily be cross-compiled/bootstraped,
> this is the root of the problem, the glibc maintainer
> doesn't consider that as an important feature).
Ever wonder why?
When you do a native build, glibc itself is involved
in the production of glibc. So, via the glibc functions
for writing a file, it could recognize itself and add
some code. You'd never see this code in the source!
All along, we thought the compiler might be backdoored.
Nobody ever thought to consider that the shared C library
might be, for example, changing the behavior of unmodified
PAM modules as they run.
>:-)
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Benjamin Herrenschmidt 2004-04-28, 11:33 pm |
| On Thu, 2004-04-29 at 10:40, Albert Cahalan wrote:
> On Tue, 2004-04-27 at 19:09, Benjamin Herrenschmidt wrote:
>
>
> Ever wonder why?
heheh ;) Well... thing is, it's _difficult_ but it can
be done (bootstrapping)
[vbcol=seagreen]
> When you do a native build, glibc itself is involved
> in the production of glibc. So, via the glibc functions
> for writing a file, it could recognize itself and add
> some code. You'd never see this code in the source!
>
> All along, we thought the compiler might be backdoored.
> Nobody ever thought to consider that the shared C library
> might be, for example, changing the behavior of unmodified
> PAM modules as they run.
>
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|