[buildpkg] mhwd-gpu --setgl mesa needs to be called in multilib #48
Labels
No labels
Done
bug
buildiso
buildpkg
buildtree
critical
deployiso
duplicate
enhancement
help wanted
in progress
invalid
manjaro-chroot
note
old-not-relevant
optional
question
sonar
todo
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tools/manjaro-tools#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Created by: manjaro
As of now mhwd-gpu --setgl gets only called in root chroot. When you try to build any lib32 pkg related on lib32-libgl it will fail. You have to call manjaro-chroot > mhwd-gpu --setgl mesa before you can compile such a package in your user chroot.
Created by: udeved
Should work with this:
8d8c029Reopen if required please.
Created by: philmmanjaro
This is still happening. I just tried to build lib32-gtk3:
Created by: udeved
Hmm, so I need to to set gl perhaps in the root chroot before it gets rsycnced as user copy.
Atm, it sets gl in user copy.
Created by: udeved
Oops, I realize, I had already chenged it to set gl in the root before the user copy is created.
I'll try with setting gl in user copy.
Created by: udeved
I know what's wrong, naturally, the chroot pulls only the devel and/or multilib-devel packages.
So mhwd is not installed in chroot, thus mhwd-gpu command fails, it is not present.
So how to fix? At mhwd package level, ie adding devel group?
Created by: alexandruianu
Maybe put some mhwd-gpu scripts directly in the tool, with a variable that can set it on or off to work after the multilib build environment is created?
Created by: udeved
Hmm, I had the impression mhwd-gpr scrip is essential part of mhwd.
The easiest would be really to add mhwd to devel group too, not only base group.
It fails because mhwd is not present in chroot, its in my view a mhwd dependency issue.
Created by: udeved
Forget about the mhwd devel membership.
The process creates a multilib devel chroot, then it copies with rsyc the root to a user copy.
From there, the PKGBUILD pulls in depends, mhwd is one of the depends.
but, how do we update the gl symlinks, lib32-mesa has not been installed yet, but mhwd has already set the symlinks for x86_64 only.
Should eventually lib32-mesa run mhwd-gpu?
Created by: philmmanjaro
Hmm, let me check it once again ...
Created by: philmmanjaro
lib32-mesa-libgl needs to been installed, as it runs mhwd-gpu --check once again.
Created by: udeved
There is no such packages.
I suspect you dropped it in favour of lib32-mesa, which comes from arch.
Created by: udeved
I think thats ugly solution, because it pulls lib32-mesa for every single lib32 packages you want to build.
Better would be to do lib32-mesa ourselves and call mhwd-gpu post_install
For example, I wouldn't need a lib32-mesa initialized chroot for lib32-eudev.
Created by: udeved
Its also no good for depends, since the initial chroot already has lib32-mesa installed.
The initial chroot is supposed to only provide the stuff you need to compile, we circumvent the pkgbuild depends.
Created by: udeved
So why don't add mhwd to devel group?
Created by: philmmanjaro
Arg, this is bull. We have to add lib32-mesa to fix it or modify that package what I don't like to do ... Hmm.
Created by: udeved
Yes, naugty, I think if we want to do it properly without any dirty hacks, we got to maintain lib32-mesa with a modified .install script.
Created by: philmmanjaro
I don't like that ... Hmm.
Created by: udeved
Well, mhwd would need a mechanism to autoupdate if libgl providers are installed.
There is no way we can hook into the process once pacman pulls the depends, and mhwd comes before the lib32.mesa.
Created by: philmmanjaro
Well, seems we have to repack lib32-mesa after all ...
Created by: udeved
I fear yes.
Created by: philmmanjaro
This is fixed with new lib32-mesa package ...
Created by: udeved
Withz the new package, we should not need any mhwd-gpu call in chroot, ie we can likely remove all the workarounds.
Created by: philmmanjaro
Check the code. I already did that ...
Created by: udeved
Great!
I already spotted it. :)