New comment by EliteTK on void-packages repository

https://github.com/void-linux/void-packages/pull/34106#issuecomment-972304584

Comment:
Since github has drafts now, I've made this one.

I got to thinking about the i686 build and I think I understand how it works.

The cpu is set to i686 because nim doesn't really support cross-building the compiler. The problem is this doesn't actually work when you try to run the compile locally (and it didn't work for the previous csources) so I'm confused there. I pushed to see what CI says about it.

I think actually the correct solution would be to do for i686 what we're currently doing for the other non x86_64 arches an I'm not sure why that isn't the case already.

But in the meanwhile, if this does end up working in CI, I would like to keep it that way and get this version bump merged. Then doing i686 builds properly can be a task for later.

That being said I think _ALL_ builds should be done the way that they are for non-x86_64/i686 and that's so you can cross-compile a nim void package from a non-x86_64 machine. But I don't know what the void policy is there.