[SOLVED] ./chromium.SlackBuild FAILED at line 1676 building ungoogled-chromium-122.0.6261.57-1

breaker · 03-10-2024, 01:47 PM

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'
ninja: error: '../../third_party/node/linux/node-linux-x64/bin/node', needed by 'gen/ui/webui/resources/tsc/cr_elements/cr_tab_box/cr_tab_box.js', missing and no known rule to make it
-- Manually installing everything.
install: cannot stat 'out/Release/chrome': No such file or directory
./chromium.SlackBuild FAILED at line 1676

Lines 1662 - 1667

Code:

if [ $USE_UNGOOGLED -eq 0 ] &&  [ ! -f out/Release/chrome_crashpad_handler ]
then
  # ungoogled-chromium has crash-reporting disabled:
  LDFLAGS="$LDFLAGS" \
  LC_ALL=C \
  ninja -C out/Release \
    chrome_crashpad_handler \
    2>&1 | tee -a $OUTPUT/ninja-${PRGNAM}.log
fi

# Manually install everything:
echo "-- Manually installing everything."

# The main binary:
install -D out/Release/chrome $PKG/usr/lib${LIBDIRSUFFIX}/${PRGNAM}/${PRGNAM}

I changed this to a 1

Code:

# Build an ungoogled chromium package (default no):
USE_UNGOOGLED=${USE_UNGOOGLED:-1}

Please advise.

solarfields · 03-11-2024, 05:49 AM

out/Release/chrome

did you check if the above exists?

breaker · 03-11-2024, 12:36 PM

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?

Windu · 03-11-2024, 01:57 PM

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;
#                  - nodejs >= 20.0.0
#                  - gcc >= 8 , llvm >= 16 for bootstrapping gn;
#                  - nasm >= 2.14 (yasm no longer being used);
#                  - cmake >= 3.24.1
#                  - python3 >= 3.7, python3-setuptools;
#                  - java runtime
#                  - Internet access (for downloading toolchain bins)

I assume that you have not installed the required build dependencies.

breaker · 03-11-2024, 04:12 PM

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.

Windu · 03-11-2024, 05:13 PM

Quote:

Originally Posted by breaker

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.

I guess you are not a regular Slackware user? All Slackware build scripts expect that you run them as the root user. No 'sudo'.

breaker · 03-11-2024, 06:33 PM

Quote:

Originally Posted by Windu

I guess you are not a regular Slackware user?

ouch! I've been using it every day for a couple of years, but did not build many slackbuilds. It has been a while, the last was a Canon printer driver. I don't use any other OS too much, except at work and a little Rasberry Pi OS, butI don't like Debian.

kgha · 03-12-2024, 05:15 AM

Quote:

Originally Posted by breaker

...but did not build many slackbuilds.

Always a good idea to check for dependencies. They're listed at slackbuilds.org (also in the .info files). AlienBob often (but not always) provides a slack-required file in the buildscript directory listing dependencies.
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?

breaker · 03-12-2024, 12:50 PM

@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?

kgha · 03-12-2024, 03:53 PM

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

breaker · 03-12-2024, 08:42 PM

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.

kgha · 03-13-2024, 02:00 AM

Quote:

Originally Posted by breaker

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 not familiar with slackpkg, having used slapt-get and its frontend gslapt for upgrading for decades. But as I understand the information at https://docs.slackware.com/slackware:slackpkg , adding [0-9]+alien to the blacklist means that packages with the _alien tag will never be replaced with packages from the official repo.

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:

Originally Posted by breaker

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.

Wow. Hopefully it's successfully completed by now. That's why I refrain from compiling some stuff (chromium, qt5/qt6, and others), not having the latest and greatest hardware, grateful that ready-made packages are available.

breaker · 03-13-2024, 01:25 PM

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.

breaker · 03-13-2024, 09:42 PM

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.

/tmp/build/package-chromium-ungoogled

kgha · 03-14-2024, 04:01 AM

Quote:

Originally Posted by breaker

Done! 29+ hours!

Setting a record