Hi Tomek,
Thanks for your response. I added a comment to the Gitlab issue directly.
Just to be clear my hope was not to get from ISC Stork package compiled for 32 bit architecture but to get source files that I should be able to compile myself on my legacy machine (like I did sucesfully with Kea 1.8.2 sources). If that is the case I will share the output of compilation errors, which I suspected were due to missing 32 bit-compatible librairies.
Valéry.
----- Mail original -----
Hi Tomek,
Thanks for your quick reply, and I fully understand the rationale behind the decision to not maintain 32 bit compiled packages for Stork. No issue with that, of course.
But my request was actually slightly different, likely not raised explicitly enough. I'd like to understand if the sources should work on a 32 bit architecture, which you seem to have confirmed positively. As written in my original post it is the case for Kea as compilation worked well for me (took just some time) but it didn't work for Stork. I thought that was due to libraries only available for 64 architecture hence not installed by my apt package manager, but I might be wrong with this assumption (being a networking guy and not a developer).
So maybe you can re-confirm if I should expect compilation of Stork source files to work on my legacy machine. In such case I will share the compilation errors in a separate post (either on this Gitlab or any other relevant ISC Stork list if available) with the hope to get guidance or fixes.
Thanks,
Valéry Augais.
Hello.
As I couldn't find on Cloudsmith repo the package for my debian system (a 32 bit architecture!) I downloaded the sources from ISC server. This approach worked fine for kea as I could compile all sources successfully. As to stork looking at Rakefile I get that only 64 bit is supported. Is there a chance 32 bit will come into play at some point?
Thanks.