#2718: Have GCC link to system zlib
-------------------------+--------------------------------------------------
Reporter: jhuntwork | Owner: lfs-b...@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.7
Component: Book | Version: SVN
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
Comment(by matt...@…):
Replying to [comment:8 jhuntwork]:
> Replying to [comment:7 matt...@…]:
> > Hmm, I'd be prone to avoid using that switch then, as I'd prefer to
avoid using static libraries if possible.
>
> I'm not sure I understand your reasoning here. If it builds an internal
copy of zlib and uses that, then it's definitely using static anyway.
Maybe "I'd prefer to avoid using static system libraries if possible."
i.e. if we're going to use a system library we'd benefit most by using the
dynamic libraries. That way, if there's a security issue with zlib, in
this case, we'd be able to fix that vulnerability system-wide by
upgrading/patching Zlib. If GCC uses its internal zlib, or the system's
static zlib, we'd have to recompile GCC after fixing the relevant copy of
zlib.
> Good call. As it turns out, it is dynamically linking to zlib:
Great, in which case I think this is pretty much a no-brainer then!
> So it appears that it uses zlib statically in some spots through the
build and then dynamically for some installed binaries.
Not sure what you mean here. I only found 4 references to '-lz' in my
build logs, referring to the binaries 'cc1-dummy', 'cc1', 'cc1plus-dummy',
'cc1plus'.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2718#comment:9>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
