Hi Kevin, On Sun, 2019-07-14 at 15:50 -0700, Kevin Fenzi wrote: > On 7/14/19 2:35 PM, John Reiser wrote: > > Kevin Fenzi wrote: > > > Neal Gompa wrote: > > > > [[snip]] > > > > > > This will also make it impossible for people to locally do multilib > > > > build/installs. It will remove COPR’s ability to do the same. For that > > > > reason alone, I don’t particularly want this change to happen. > > > Can you expand on what you mean by 'locally do' ? > > > > I want to run "gcc -m32 -o my_app-i686 *.o ..." locally on my own box > > to build executables that run as 32-bit apps on multilib x86_64. > > For some apps 2GB of malloc() arena is plenty, and they run faster > > in 32-bit mode because a 64-byte cache line contains 16 pointers > > instead of only 8. > > This should still work, unless there are libraries you use that are not > multilib. > > > [[snip]] > > > > > Finally, if you would prefer this not happen now, is there a time when > > > you would further down the road? Whats the critera/goalpost/cutoff? > > > > One year after Red Hat Enterprise Linux version 7 reaches end-of-support. > > It would be handy for Fedora to have 32-bit *-devel packages until then. > > We will still have 32bit devel packages in the x86_64 repos after this > change. It doesn't affect multilib at all. It only stops building and > publishing the 'pure' i386 repos on the mirror network. > > I don't think we can drop multilib until at least steam/wine are ready > for it at least. Being able to build 32bit is useful during development too. It is much easier to expose some memory issues. For example fuzzing some applications is best done against the 32bit variant to reduce the memory search space. So imho making sure Fedora is a good developer distro makes sure multilib gcc -m32 keeps working. So you need at least the foobar-devel.i686 libraries in your x86_64 repository. Could you explain a bit more how this (keeps) working? I think my mental model of how Fedora repositories work in the case of multilib devel packages is a bit flawed. At first I assumed that this suggestion would kill that. Because I was under the impression that it worked by having the i386 repository be part of the x86_64 package repository. So removing the i686 repositories would mean removing all 32bit packages from x86_64. But from your explanation above it seems that is not how it works. So if there are no i686 repositories, then where/how do the 32bit multilib packages come from? I think I am mixing up buildroots, koji targets, repositories in my mind. For example I maintain two packages that provide 32bit multilib binaries. They are produced by the i686 koji target. Then elfutils- devel.i686 (to create 32bit multilib binaries) and valgrind.i686 (to run 32bit multilib binaries) are provided to the user because the i686 repository is part of the x86_64 repository (if I understand things correctly). Will this just keep working, or will I have to make changes to my packages to keep this working after the disappearance of the i686 repository? Thanks, Mark _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
