From: | "Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx> |
Date: | Sun, 16 Dec 2007 14:47:05 +0100 |
Alex Neundorf wrote: >> As soon as you compile stuff, you probably will get different binaries. >> If you update the kernel, you need to update the userland as well. >> >> If we had a way to identify from which sources a binary was compiled >> from, we could do upgrades more easily. Maybe enhance gcc to include a >> checksum of the sources into the object? > I'm not sure this would be enough. > The stuff could be compiled with other features enabled (which use other > libs), other compiler/linker options, so it has different dependencies etc. changed options usually change the sources, i.e. config.h or -Defines= will change the preprocessed source code. Maybe I should have explicitly mentioned this: I was thinking about the preprocessed source code (the stuff cc1 works on). Statically linking with a different binary will produce a different list of objects. Dynamically linking should be no problem, unless you link to different libraries. Compiler options could indeed a problem, but then, which options influence the binary and shouldn't be ignored? The only thing I can think of is the stack protector, for instance, which in turn will lead to different link lists. cheers simon
Attachment:
signature.asc
Description: OpenPGP digital signature