Parrot-Developers/olympe

BUILD ISSUE (MAKE ERROR DETECTED)

eyadkurdi opened this issue · 7 comments

Hello Guys,
I am installing parrot-olympe 7.6 on ubuntu 20.4 (core version) using pi4
each time i try to build i got

12

MAKE ERROR DETECTED
[E] Command failed (returncode=254

Hi I am running into this same issue,

I have python3.9 downloaded and set up with the proper alias's. Yet my install still tries to check version of python3.8

I am building on a Jetson Xavier btw

@eyadkurdi @Carson-Bay
I discovered that this is being caused by the clang package. For whatever reason the version clang is returning is garage. I was able to workaround this by setting line 296 in ctypeslib/codegen/cindex.py to version = package.version.parse('14.0') as I had the build system install clang==14. Also, be sure to only install auditwheel==5.4.0 or lower 6.0.0 will cause issues when building.

Btw, Raspbian is fine to use as an OS for Olympe since its Debian based. That's what I'm using on my Pi with success.

Thanks a lot @bradylangdale

@bradylangdale
it didn't worked for me
my clang version is '14.0.6'
auditwheel==5.4.0

I set the line version = package.version.parse('14.0') and also tried with version = package.version.parse('14.0.6')

but still facing the same error
Screenshot from 2024-07-19 11-10-44

@HarisAfzal7

That's because you're dealing with a separate issue. The stack trace is complaining about the wheel not having enough arguments, while the builds above are about invalid version tags. However, I also encountered what you're experiencing. You need to either upgrade or downgrade Python's setup tools. The logs mention upgrading so you could start there. I might still have this repo building in which case I could make a build to share.

@bradylangdale it didn't worked for me my clang version is '14.0.6' auditwheel==5.4.0

I set the line version = package.version.parse('14.0') and also tried with version = package.version.parse('14.0.6')

but still facing the same error Screenshot from 2024-07-19 11-10-44

@HarisAfzal7 The build issue you're reporting here is what has been describred in #55 and should be fixed in the just released v7.7.5