search

pharo-project / pharo-zeroconf

ZeroConf script generator for http://get.pharo.org
16 stars 15 forks source link

AppVeyor builds for Pharo on Windows fail because there's no i686 architecture #32

Open theseion opened 3 years ago

theseion commented 3 years ago

The zeroconf script reads i686 as architecture from AppVeyor for Windows builds. This is correct but there is no associated VM. The script used to select a correct VM before the architecture was included in the filename.

Example: https://ci.appveyor.com/project/theseion/fuel/build/job/w0wvw4vq2lx01dj2

theseion commented 3 years ago

I've opened #33. It adds a case statement to try and map the architecture to something sensible. I've also regenerated the scripts for Pharo 9 only.

theseion commented 3 years ago

Since there are no longer any 32-bit VM's for Pharo 9+ this issue is moot. The issue arose because of a misconfiguration that led to the platform being 32-bit instead of 64-bit, hence the different architecture.

guillep commented 3 years ago

Hi Max, there should be 32 bit vms for Pharo9+. Of course there are no for OSX, but for some unixes it happens (like raspbians), and windows (modulo you can run bash).

I'm running with deadlines, but I'll take care of it ASAP, this is important :)

theseion commented 3 years ago

Great, thanks!

In that case, I think we should probably use a common identifier for 32-bit architecture, except for special ones (like we have for ARM 64). I would suggest x86, that's probably common enough for people to know what it means. Then we can map all ix86 architectures to x86.