NodeJS need rebuild without LTO #57
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NodeJS as failed to build because of LTO and this is blocking chromium to be build and others packages
By the way, it seems like ALHP is wanting to build the version of nodejs in testing
Well it shouldn't block chromium if you have your
pacman.confas described in the README.md https://git.harting.dev/anonfunc/ALHP.GO#example-pacman-confOr I misunderstand.
nodejsneeds to be on the LTO list, indeed.The builder does not wait for its own builds, since it always builds with vanilla packages. ALHP is truly waiting for
nodejs-17.1.0-1, because it is 'released' as far as Archlinux's own svn2git is concerned, see here: https://github.com/archlinux/svntogit-community/tree/packages/nodejs/repos/community-x86_64.As soon as something is in
repos/reponame-arch/, ALHP assumes it is build and live on Arch (and waits for it to show up on its mirror). Sadly, some maintainers don't follow that structure exactly. If you look at svn2git fornodejs, you'll see that thecommunity-testing-x86_64version is already incommunity-x86_64, which should be the current live version from archweb (16.11.1-1).This will resolve itself after it moves out of testing, but it sure is annoying. Implementing logic to fix that would unavoidably lead to some request to archweb (since its the only source remaining telling the real story), which I would like to avoid.
I think the weird thing is that the chromium package doesn't have a specific version named like
nodejs<17or something, so it a little strange that it still want to wait for nodejs to be buildChromium doesn't need to have nodejs as a dep, it just need it to build
Not all packages (that need version constraints) have version constrains. You can't assume all packagers/maintainers are going to add them, they are optional after all. Its better to make sure we have all the latest deps. available to build that were also available to the official build.
makedependencies are dependencies too. (obvious from the name)
I mean yeah i agree with you, it sure would be a nightmare to manage
Since 'importing' gentooLTO's exemptions I think we can close this now. If new
nodejsversions still fail to build please reopen this.Reopening this issue since NodeJS failed to compile with the new version, i think we can add it to the LTO blacklist.
It is already on the blacklist, and the current build is not new either. Remember that ALHP already had 17.0.1-1.
Ho yeah my bad, sorry i'm closing this now then, and wait for the
7.0.1-2that is soon going to be build then, my apologies.