On Thu, 2017-01-05 at 11:03 -0500, Stephen Gallagher wrote: > # Overview > > For many years, Fedora has supported multilib by carrying parallel-installable > libraries in /usr/lib[64]. This was necessary for a very long time in order to > support 32-bit applications running on a 64-bit deployment. However, in today's > new container world, there is a whole new option. > > I'd like to propose that we consider moving away from our traditional approach > to multilib in favor of recommending the use of a 32-bit container runtime when > needed on a 64-bit host. I think this is missing the developer story. I maintain a couple of tools that currently need to handle 32-on-64-bit setups and it is a bit of a pain. So getting rid of multilib certainly would make my life easier. But some of those tools really do work better because they are 64-bit themselves but target 32-bit applications/libraries. It means they can use the full 64-bit address space while reading/writing 32-bit files/datastructures. I believe gcc and binutils/ld are in the same category. Some applications targeting 32-bit architectures are so big that you need 64-bit tools to just build them. Maybe this is a small enough development story that it doesn't really matter. But it would be good to know if developers are comfortable with a pure/native 32bit-only development toolchain. Thanks, Mark _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
