building ungoogled-chromium from ports

after almost 24 hrs and using ai for help to solve numerous problems and entering my root password 100 times or more, i am finally nearing the end of the crazy build

ninja: Entering directory `/usr/ports/www/ungoogled-chromium/work/chromium-146.0.7680.80/out/Release/gn_build'


i wondered why it wasn't available for install with a pkg command but really i see it's a marathon effort to build from source. i'm guessing that must be why.

and of course i don't know what i am doing at all so i have no idea if any of the many options i selected along the way are the right ones or not. this build was clearly 'above my paygrade'
 
If you entered the root password multiple times you did build dependencies as well.

Even if your desired port is not available as a package most or all build dependencies will be. Install them as packages before building the main port.

And you can start the whole build as root, then the password questions don't come up.
 
If you entered the root password multiple times you did build dependencies as well.

Even if your desired port is not available as a package most or all build dependencies will be. Install them before building the main port.
yes that seems right. soo many.. crazy number.
 
i wondered why it wasn't available for install with a pkg command but really i see it's a marathon effort to build from source. i'm guessing that must be why.
Good guess:

https://pkg-status.freebsd.org/beefy21/build.html?mastername=150amd64-quarterly&build=05fed70d47d6 .

"Reason: Blacklisted"
Poudriere bulk results for 150amd64-quarterly 05fed70d47d6.png


See also
 
ok so why was it black listed?
Because it chokes up the process, so now only the regular www/chromium gets built, something that took almost 25 hours by the way.

I don't think it's still blacklisted looks like it's queued up
The Queued ports section is the total of all ports that are set to be built. That doesn't mean they will all end up being built. If you see www/ungoogled-chromium in the Ignored ports section, then it will be ignored. By the way, this build is already finished and www/ungoogled-chromium is not listed in the Built ports section.
That's been the case for months now (since late last year) and probably won't change any time soon.

https://pkg-status.freebsd.org/beefy23/build.html?mastername=150amd64-default&build=5d5e50b67111
 
Hey lookie there after 24 hrs is of building u-chromium i'm 78% done!

Code:
[ 78% 25429/32586]
AI Overview

If 24 hours represents 78% of a task, it will take approximately 6 hours and 46 minutes more to reach 100% completion.

Calculation Breakdown
  1. Calculate Total Duration: Divide the elapsed time by the current percentage (expressed as a decimal) to find the total time required for 100%.

  2. Calculate Remaining Time: Subtract the hours already spent from the total projected time.

  3. Convert to Minutes: Convert the decimal portion of the remaining time into minutes by multiplying by 60.

    ✅ Answer It will take 6 hours and 46 minutes to reach 100% completion
My 2400 GE processor is getting quite the workout! Just look at those conky stats!
2400ge  workout.jpg

I may def have to revisit adding more swap space.

and after 2 days of being put through it's paces the temp seems ok..

Code:
Sensors:
  System Temperatures: cpu: 66.0 C mobo: N/A
  Fan Speeds (RPM): N/A
the old gurl holds her own.
 
Oh hi! I use 4300 GE, too! 👋 😁
CPU:
Info: 8-core model: AMD Ryzen 5 PRO 2400GE w/ Radeon Vega Graphics bits: 64
type: MCP arch: Zen rev: 0 cache: L1: 384 KiB L2: 2 MiB L3: 4 MiB
note: check
Speed (MHz): 3200 min/max: N/A cores: No OS support for core speeds.
Features: avx avx2 lm nx pae sse sse2 sse3 sse4a ssse3 svm

[ 90% 29659/32586]
woo hoo
finally done building ungoogled chromium.jpg
 
I have no idea and, at the same time, I suspect you cannot do that. Let's call cracauer@. He's a nice enough fellow. He'll answer very succinctly, but you can ask him further questions.
Well, I guess he decided no to answer the call. Sorry about giving you false hope. Anyway, I'm quite sure that you not being part of the FreeBSD commiters and whatnot, you cannot upload your binaries anywhere. Thanks for the thought, though. For me, why ungoogled-chromium is not part of the packages remains a mystery. Maybe there are insidious interests at play. I prefer to believe there are not.
 
well ai has the following to say

AI Overview
To extract and share your custom-built ungoogled-chromium as an installable binary package (a
.txz file) on FreeBSD, the recommended method is to use the Ports infrastructure and tools like poudriere or portmaster. Manually extracting the binary and all its dependencies is complex and error-prone due to the sheer number of shared libraries and configuration files involved.
Here is the general procedure:

Set up the Ports environment: If you don't already have it, get the FreeBSD Ports Collection using git clone https://git.freebsd.org/ports.git /usr/ports.
Use poudriere (recommended for sharing): Poudriere is the official tool used to build packages for the FreeBSD project. It builds packages in a clean, isolated environment (a jail) and creates a package repository for easy sharing and installation.
Install poudriere using pkg install poudriere.
Configure poudriere and set up a build jail and ports tree (see the FreeBSD Handbook or DigitalOcean tutorial for detailed steps).
Use poudriere to build www/ungoogled-chromium from the ports tree. The resulting .txz package will be in the /usr/local/poudriere/data/packages/ directory.
You can then copy the generated .txz file and share it. Other users can install it using pkg add /path/to/package.txz.
Alternatively, use make package within the port's directory: If you built the software by navigating to /usr/ports/www/ungoogled-chromium and running make install clean, you can try using make package in that directory. This often generates the .txz file in a work/pkg subdirectory. This method is simpler for a single, one-off package but may not handle dependencies for other users as robustly as poudriere's repository method.

Using the built-in FreeBSD packaging tools ensures that all necessary dependencies and configurations are correctly bundled, allowing others to install your binary package smoothly with the pkg command.


And if i chose to go that route i could upload it anywhere...
 
I was compiling it a couple of years ago when I was on Linux and before I went FreeBSD desktop full-time. Compiling ungoogled chromium took a long time, several hours. I haven't done it for a while because I switched to Firefox. Firefox compiles in five seconds on FreeBSD. 🙃 And I unmozilla my Firefox in five seconds too. :)
 
Even an official package with a checksum and the label "ungoogled" on it isn't trustworthy to me - it's far too much code from a company that isn't acting in my interests at all; I only use that browser for testing, and not for everyday use. And I use VMs as well as different user accounts.
 
Back
Top