My first question. Apologies if I miss the obvious.
I am currently using 32 bit legacy code to export the content of binary legacy files for further processing under 64 bit. To do so, I have to modify and recompile the legacy code.
Worked nice until I switched to version 44; now I am getting
“/usr/bin/ld.bfd: /usr/lib/libatomic.so.1.2.0 kann nicht gefunden werden: Datei oder Verzeichnis nicht gefunden”
i.e.:
/usr/bin/ld.bfd: /usr/lib/libatomic.so.1.2.0 cannot be found: file or directory not found"
Attempts to reinstall gcc or libatomic for 32 bit failed.
What have I overlooked?
note: On the 64 bit side, everything runs smoothly.
Thanks in advance,
Manfred
Sorry, issue is resolved. I overlooked the drop of 32 bit support in 44. Sigh. As the legacy code is about 250.000 statements it means to freez this box at 43.
Manfred
I would create a f43 VM (use libvirt/virtual machine manager) to support your legacy app that you freeze with your app working.
Then you can upgrade you main system without worrying about the app breaking.
Thanks a lot, I’ll try that.
Will acknowledge when done, might take some time however.
Quite lot of 38 bin libraries and packages are built and never distributed. You can find them at the koni site, for example https://koji.fedoraproject.org/koji/buildinfo?buildID=2997047 has the libatomic-16.1.1-2.fc44.i686.rpm package you can download. You do have to resolve possible dependencies yourself, though.
Given the push to stop build any i686 packages in Fedora, I think the VM for a legacy app is the future proof route to take.
Once the 64 bit steam comes out of beta this year I do wonder what 32bit support Fedora will need? Steam being one of the reasons that 32 bit RPMs are still being built.
The 32 bit libatomic is still present in the Fedora 44 repositories:
% sudo dnf list --available libatomic
Updating and loading repositories:
Repositories loaded.
Available packages (available for reinstall, available for upgrade)
libatomic.i686 16.1.1-2.fc44 updates
libatomic.x86_64 16.1.1-2.fc44 updates