/usr/include/clang/14.0.1
and the new chromium failed to build because of that? Just downgraded and it started compiling fine
build() {
mv clang-tools-extra-$version.src clang-$version.src/tools/extra
prt-get isinst ccache && PKGMK_CLANG+=' -D LLVM_CCACHE_BUILD=ON'
cmake -S $name-$version.src -B build -G Ninja $PKGMK_CLANG \
-D CMAKE_INSTALL_PREFIX=/usr \
-D CMAKE_INSTALL_LIBEXECDIR=lib/clang \
-D CMAKE_BUILD_TYPE=Release \
-D CMAKE_C_FLAGS_RELEASE="$CFLAGS" \
-D CMAKE_CXX_FLAGS_RELEASE="$CXXFLAGS" \
-D LLVM_MAIN_SRC_DIR="$SRC/llvm-$version.src" \
-D LLVM_EXTERNAL_LIT=/usr/bin/lit \
-D LLVM_PARALLEL_COMPILE_JOBS="${JOBS:-1}" \
-Wno-dev
cmake --build build
DESTDIR=$PKG cmake --install build
}
--disable-features=GlobalMediaControls
that still works
Extract chromium source
git init
git add ./path/to/file1 ./path/to/file2 ...
git commit -am "init"
Make changes to file1, file2 and whatever else you passed to git add
git diff HEAD > my.patch
ERR_CERT_AUTHORITY_INVALID
- is there anything know about this? My first quick google search didn't yield anything
Well there's an easy explanation for that: Your workplace is using self signed certificates for those sites which were not signed by a public certificate authority
For security reasons a browser will only trust a list of known public authorities like LetsEncrypt which are known to thoroughly check the ownership of a domain before signing a certificate. If this wouldn't be the case, browsers would have no way to verify that a server they are talking to is actually the server they want to talk to
For ungoogled-chromium to accept a custom authority you need that authorities certificate and add it in the browser's settings
maybe vanilla / ungoogled chromium ignores the client's certificates?
I'm not sure about that
What could also be is that you previously told the browser to ignore the invalid certificate
Version 102.0.5005.61-1 and 102.0.5005.61-2 have a bug that removes the option to bypass certificate errors (-3 will fix that)