![]() ![]() In any case, this is really a trivial issue. My suggestion for the doing this here is just the same as what we've done elsewhere. All throughout BLFS there are switches used to link to the system installed zlib instead of included versions. Actually, when including BLFS packages, zlib is one of the most used libraries. I do know why we build gmp and mpfr separately, and for the same reasons we've already built zlib and put it way up in the build order. We're using a switch that they put there for that purpose. Why nervous? It's not like we're hacking the GCC code (a feat we've done more than I'd like in chapter 5). Trivial, I know, but to me, the reason for doing this is less about saving time and more about using the build method to our advantage. I halted it after I saw it building zlib and started looking for the switch to use, but it had already been going for at least twice that amount. I have no idea why gcc needs libz anyway. ![]() We build gmp and mpfr separately so other programs have them available. ![]() Replying to using -lz within the build, so I believe all uses are of the static library.ĭefine 'much longer'. As it is, since you install those to the system in chapter 6 solely for the sake of GCC, then you're already setting a precedent. I would accept this as a potentially valid argument if you applied that same principle to the other libraries that gcc uses and could be built in statically, namely, gmp and mpfr. I don't see other distros doing this and the potential to do harm is greater than what appears to be a negligible benefit. It would require moving zlib to a position before gcc in Chapter 6.Run through a build, you'll see what I mean. In any case, the version of zlib that comes with gcc is an older one and for some reason it takes much longer than 5 seconds. It's using -lz within the build, so I believe all uses are of the static library.Īny time that can be saved is worth considering saving. On my system that has been built with the -with-system-zlib switch: Replying to It creates another potential way to break gcc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |