Fix Plume arm builds #427
No reviewers
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#427
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "llvm-multiarch-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
llvm latest svn commit is broken as of 2019/01/12. This patch pins the llvm+lld versions used for arm compiles.
It also tweaks the architecture detection to be more reliable in multi-lib/multi-arch situations where the CPU is 64bit but the runtime is 32bit.
Codecov Report
@ -4,0 +15,4 @@print('amd64', end='')elif processor == 'armv7l':print('armhf', end='')EOFhow big is the chance that anyone's still using i386?
@ -4,0 +15,4 @@print('amd64', end='')elif processor == 'armv7l':print('armhf', end='')EOF@igalic the main linux kernel dev's have suggested dropping i386 support...
If it's something others run into I'm happy to add it back but i need the platform.machine() output to add it to the conditional. I don't have access to i386 and didn't want to add an arch that I don't have valid output for.
@ -2,2 +2,3 @@ARCH=`arch`ARCH=$(python <<EOFfrom __future__ import print_functionWouldn't it be possible to do the same with Bash? And maybe you could use Python 3 if it present instead of importing from
__future__.@ -2,2 +2,3 @@ARCH=`arch`ARCH=$(python <<EOFfrom __future__ import print_functionyes. with great difficulty.
+1
@ -2,2 +2,3 @@ARCH=`arch`ARCH=$(python <<EOFfrom __future__ import print_function@BaptisteGelez I was trying to do this in bash initally and... it ended up being easier to read and maintain with python.
Re python 2/3 ; the code in question will run under both. Ubuntu and Debian still have python2 as a default and the slim docker images don't include both by default. I wanted to keep the code as generic as possible so additional dependencies won't be necessary if it's used elsewhere.