Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linux x86_32 not building in buildbot #11

Open
markwkidd opened this issue Feb 19, 2018 · 5 comments
Open

linux x86_32 not building in buildbot #11

markwkidd opened this issue Feb 19, 2018 · 5 comments

Comments

@markwkidd
Copy link
Contributor

I just noticed that the buildbot does not have x86_32 binaries for FreeIntv.

For reference, the buildbot does have x86_64 binaries for Linux as well as x86_32 and x86_64 binaries for Windows.

I've been trying to set up a msys2/MinGW32 environment in my Windows 7 system to attempt cross-compilation but I've run into problems with the environment.

@RobLoach is there any chance this is one of the buildbot platforms you're familiar with? @fr500 I know you are well-versed in the buildbot -- do you see any red flags in the FreeIntv Makefile?

@RobLoach
Copy link
Member

Is x86_32 even a thing?
http://buildbot.fiveforty.net/admin/buildbot/build/?q=linux

I don't see it building any cores of 86_32.

@markwkidd
Copy link
Contributor Author

markwkidd commented Feb 19, 2018

I can't follow that link, but now that I looked at the public buildbot site I should apologize that x86 (32bits aka x86_32) is labelled simply x86: https://buildbot.libretro.com/nightly/linux/x86/

Compare that to Linux x86_64 and you'll notice FreeIntv is missing: https://buildbot.libretro.com/nightly/linux/x86_64/

@ghost
Copy link

ghost commented Feb 19, 2018

We no longer build cores for linux x86, the ones that are up on the buildbot are all very old (from 2016).

@RobLoach He just means regular x86... some people use x86_64 to refer to 64-bit, so x86_32 is a bit less ambigous than x86 as an arch descriptor.

@markwkidd
Copy link
Contributor Author

markwkidd commented Feb 19, 2018

Thank you @bparker06 for explaining that.

some people use x86_64 to refer to 64-bit, so x86_32 is a bit less ambigous than x86 as an arch descriptor.

Is there any other way to refer to amd/intel 64-bit than x86_64? If so, then it seems like x86_32 is the clearest way to refer to the 32-bit version of that architecture (shrug)

In the Lakka realm there are many -- I think -- who are using 32-bit Linux binaries. It's sad to find out that I can't use the buildbot to add new or updated cores to Lakka x86 32-bit installations as I was hoping to do with the FreeIntv core and a Lakka 2.1 x86_32 build I'm working on.

I had been interpreting the lack of a buildbot x86_32 FreeIntv core as indication that the Makefile was broken for that environment. It sounds like that isn't really the case.

At any rate, my immediate personal and ulterior motive is to help make sure that Lakka x86 (32 bit) has access to a working FreeIntv binary. Maybe I'll take this issue to the Lakka repository so as to make sure it can at least be part of the prebuilt x86_32 binaries with the next Lakka release.

@inactive123
Copy link
Contributor

I'd like to be able to build 32bit linux cores again.

Whoever can make this happen and wants to do some manual buildbot work with us, let's meet please on Discord so we can get this automated on the buildbot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants