Fedora Core 4

[Arjan van de Ven]

On Sat, 2005-01-15 at 14:23 +0000, Mike Hearn wrote:
> On Sat, 15 Jan 2005 08:49:25 +0100, Arjan van de Ven wrote:
> > FORTIFY_SOURCE is compatible; what it does do is make the binary depend
> > on glibc 2.3.4 or higher, but well you run that risk anyway; apps
> > generally depend on the glibc (or higher) they were compiled against
> 
> Presumably it's possible to disable the FORTIFY_SOURCE extensions at
> compile time with a new gcc flag, right? ie, if you don't want a
> dependency on such a new glibc release you should be able to avoid it.

FORTIFY_SOURCE is by far not the only thing that might make your
binaries require a "new" glibc. If you want to run against an old glibc,
you should build against such an old glibc. Example: NPTL threads. 
There are countless other examples of things that make your app require
a newer glibc *IF* you build against a new glibc.
If you don't want that.. don't do that then.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20050115/808c4096/attachment-0002.bin