./chromium.SlackBuild FAILED at line 1676 building ungoogled-chromium-122.0.6261.57-1
Well, I had a big old post about this, but this damn site said could not post due to a missing security token, so I lost an hour's worth of composition.
Basically what the subject said. I never tried this before. Got it from alienbob's build directory. I tried to build as root because the normal user gave errors related to chmod. Here is where the process stopped Code:
ninja: Entering directory `out/Release' Code:
if [ $USE_UNGOOGLED -eq 0 ] && [ ! -f out/Release/chrome_crashpad_handler ] Code:
# Build an ungoogled chromium package (default no): |
out/Release/chrome
did you check if the above exists? |
I want to check, but I don't know the prefix of that path. If it is in /tmp I did not find it. I guess I can search the entire system for /out
Do you know where and by what in the script this is created? |
You seem to be running Slackware 15.0. Look at the error you post - it says something about 'node' missing.
Slackware 15.0 does not contain nodejs but if you read the script header at https://slackware.uk/people/alien/sl...ium.SlackBuild you see that: Code:
# Build needs: - ninja; |
Ah ha! I did not realize that. I will install nodejs and try again. Thanks!
As far as my first attempt, is it usual for a slackbuild to need root access, or sudo? My normal user account is not in the sudoers group. I did not look into why chmod was being called and failed exactly and I just did su to get it going. |
Quote:
|
Quote:
|
Quote:
README files (the name says it all) often give important information on compiling. A bit curious, though - why compile chromium-ungoogled when AlienBob offers a ready-made package? |
@kgha
Thanks for the tips. Also I saw I need to run su with the -l option. Yes, now I realize I could have just downloaded the ungoogled Slackpackage. I got to the regular alienbob Chromium package by doing a web search. Previously, I was unaware these existed. I did not explore his directory of packages before I set off to build the ungoogled using his Chromium/build files. So it was mostly a mistake. However, I decided to do it anyway so I could add my Google API keys. I'm unsure if I care about having them or not, however. I added and updated the dependencies, except llvm, which I forgot to do. Hopefully it builds now. I noticed there is a higher version of llvm in the Slackware extras. Do I removepkg the old, grab the one from extras, and installpkg? Also, since cmake was updated from an alienbob package, I should blacklist cmake. Would I do cmake or cmake* for that? |
Just grab the llvm-17 package from /extra and upgrade with upgradepkg. Should you for some reason need to compile something against the older llvm, grab the llvm13-compat package from /extra and install alongside the new version.
As for blacklisting it might be a good idea to blacklist everything from AlienBob with [0-9]+alien See https://docs.slackware.com/slackware:slackpkg |
Cool, yeah I did that today for alien, but I was not sure if the update went off of the Slackware list, or off the list of what you have installed. In other words, If I have 1alien cmake but I grab the list with update, will it want to grab the old cmake again?
I'm currently building the ungoogled - for the last 10 hours! This is an old PC from 2011, but I'm curious how it will go now. |
Quote:
If you use 3rd party packages, e.g. AlienBob's, you may want to look at the slackpkg+ extension: https://alien.slackbook.org/blog/int...-repositories/ Quote:
|
Yes, I do want to check out the slackpkg+, thanks.
Well, it is still building after 24 hours. I started it before work yesterday, and it was still going when I left for work today. I suspect it could be done by the time I get home. |
Done! 29+ hours! :) Version 122.0.6261.57 (Official Build, ungoogled-chromium) (64-bit)
I'm posting from this browser. Code:
Slackware package /tmp/chromium-ungoogled-122.0.6261.57-x86_64-1alien.txz created. |
Quote:
|
All times are GMT -5. The time now is 07:17 AM. |