-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Troubleshooting building the binary package on Ubuntu 24.10 #352
Comments
Hello @Ashkian,
Not an issue. That is simply the automated patching system dropping patch hunks for files that have been removed from ungoogled-chromium.
You have LLVM-16 packages installed. None are listed in the set of commands you gave, but they must have been either present on your system beforehand, or installed as dependencies of one of those packages. Make sure that you have only LLVM-19 packages installed. A combination of the two will result in an old linker reading code from a new compiler, which doesn't work. |
Hello @iskunk and thanks for reply, |
You'll need to review the list of packages installed on your system, using e.g. |
Thanks for the @iskunk advice,
warning: code will never be executed [-Wunreachable-code]
warning: 'USE_SYSTEM_ZLIB' macro redefined [-Wmacro-redefined]
warning: label at end of compound statement is a C++23 extension [-Wc++23-extensions]
warning: add explicit braces to avoid dangling else [-Wdangling-else]
warning: field 'should_autocollect_' will be initialized after field 'search_engine_choice_service_' [-Wreorder-ctor]
clang details
|
Generally, if the issue is only a warning and does not prevent the build from completing, it can be ignored. Some of those warnings are familiar and have always been present in the build. |
1 -running the following command results the following message, what does it mean, is it a issue?
command:
make convert
result:
2- running the following command results the following message, how to solve the issue?
command:
dpkg-buildpackage -b -uc
result:
Steps on Ubuntu 24.10:
The text was updated successfully, but these errors were encountered: