|
Problem compiling Chromium-ungoogled on a raspberry pi 4 with SARPI (SlackWare ARM-Current RPI)
Hello guys n' girls and slackers.
I am trying to compile Chromium-ungoogled on my raspberry pi 4 installed with SARPI (Slackware ARM -Current) uname -m shows: Quote:
Quote:
as i had to install to get the correct driver for the graphics card and sound card. Quote:
Managed to edit/change the script so it starts to compile google's clang. But here is where i get stuck as it complains that there are no compatible triple. Quote:
Weird thing is that the clang Driver never seems to be able to detect the correct triple: Starting the compile of clang it shows: Quote:
Quote:
The diffrent targets i have tried in the build script are: Quote:
Quote:
Best regards: Minime |
Quote:
But if/when you are curious to know... Code:
root@slackware:~# gcc -dumpmachineOther cflags that may be of interest... Code:
root@slackware:~# echo | gcc -v -E - 2>&1 | grep cc1 |
Quote:
So if i understand you correctly i should just leave the compile flags empty?. Quote:
And also tried adding "arm-slackware-linux-gnueabihf" as target in the build script. If i understood you correctly? Quote:
I have been using these compile flags: Code:
SLKCFLAGS="-O2 -march=armv7-a -mtune=cortex-a72 -mfpu=vfpv3-d16 -mfloat-abi=hard"Thanks for the tips, i'll give it a try removing the flags, and some hybrid of your flags to see if that helps i guess. |
Quote:
If anything, avoid -march and -mtune flags altogether. The -march flag specifies the target architecture. The -mtune flag specifies the target microarchitecture. You don't need these when compiling natively on ARM architecture. If you were cross-compiling on x86 then it would be a different matter. [EDIT] Thinking about it, all you should ever need in general when compiling natively on ARM is... Code:
SLKCFLAGS="-O2 -mcpu=native"Quote:
|
@Minime_2003 you can download the Slackbuild of Chromium 90 of BrunoLafleur
It is a repackaging of the Debian archive, and it works very well on RPI4. https://github.com/BrunoLafleur/pbsl...s/sbo/chromium |
Quote:
However as i looked more closely to the compile logs and realized in despair that the script never passed any cflags or cxxflags at all. Wasted hours doing this :( :doh: No clue if it makes any diffrence, but i added this code to the script: Code:
if [[ "$ARCH" =~ arm.* ]]; thenDont know how relevent or old this is, but i figgure its worth a try? So i´ll be puting it back to compile again for about the 10000´s time now, and will see if thsi changes the result. :) Thanks for all your tips and i´ll keep this updated on how-it all goes. Quote:
|
Quote:
In order to be successful, first you need to meet failure many, many times. In my view, those who succeed first time don't learn much. If you're anything like me you'll welcome failure as a means of learning what's right or wrong in all things. However, there can come a time when constant failure can drive someone away from their vision and goals. BrunoLafleur's GitHub repo that Desiderius gave the link to is simply repackaging the software - which means you don't have to waste time and effort building it yourself. If all you want to achieve is for it to work then that may be your best and easiest option. |
Quote:
Quote:
And to try something new one has to wait yet another 5-6 hours...really time consuming thats all =) But i don't mind learning from what i am doing and trying to achieve. Quote:
However i don't like adding loads of third party (Non slackware libs and dependencies) and i´d like to see if i can get chromium to be able to use Widevine on ARM which i suspect is not even possible if using a debian build for ahole lot of reasons. |
@Desiderius, thank you!
Quote:
|
Quote:
https://www.gnu.org/software/make/ma...s-Summary.html |
Quote:
where everything is located. however i suspect the script is using some kind of "-j" command, as i can see 4-5 threds of the compile prosseses when looking in "top" during the build. Cant say that its worth trying to get the compiler to keep going when the compilre reports googles clang compiler as broken (Needed later to compile chromium). So its ok for it to stop there as the error comes at the end when the system is to test the compiler for errors. I dont get eny other other errors during the compile, so i dont know why or how to get around nore solve this issue? But as it looks at the moment, its not possible to build googles clang on Slackware Arm... So i´v been thinking, would it be possible to ise the systems clang version? How-to solve the problem with googles build using lld as this does not exist in the system? No worries, all tips and idears are more than welcome and I really appreciate it. |
Quote:
|
Quote:
Ex. if one uses x86_64 the script downloads googles prebuilt llvm/clang binaries to compile chromium. If you use i686 the script downloads googles llvm/clang source code and compiles it with gcc i think, then after it has compiled llvm/clang it switches to googles llvm/clang to compile chromium. Gave up trying to compile googles llvm/clang on arm, as i looks it does not support building this on arm systems. So the new goal is to get the script to compile by using the systems own clang instead. |
Quote:
Code:
/usr/bin/chromium@Desiderius which libjsoncpp.so you have installed? |
Quote:
|
| All times are GMT -5. The time now is 04:26 AM. |