Failed to compile libepoxy

[rodrgz]

I was trying to compile libepoxy. The option has-dlvsym was considered as an unknown option, and the error message was

I don't know how to circumventing it...

[echawk]

I'm not sure what could be causing this; I can compile it fine on a fresh chroot. Can you post the log file?

[jason123santa]

I have the same issue when I try to compile xorg

[echawk]

@erikrodrgz @jason123santa Can you both post a log when you run the following:

sh -x /usr/bin/kiss build libepoxy or sh -x /usr/bin/kiss build xorg-server respectively? I haven't been able to reproduce.

[rodrgz]

@erikrodrgz @jason123santa Can you both post a log when you run the following:

sh -x /usr/bin/kiss build libepoxy or sh -x /usr/bin/kiss build xorg-server respectively? I haven't been able to reproduce.

https://pastebin.com/52PFfcvB

[echawk]

Thank you for the log, I think the issue you are running into is on line 52: That the Run-time dependency of gl wasn't found. Are you using a forked version of mesa? If not, try rebuilding mesa then trying again. And if you are, try using the upstream version.

Also I have the same warning when I compile libepoxy, where is says that the option is unknown. I'll drop this from the build script

[rodrgz]

Thank you for the log, I think the issue you are running into is on line 52: That the Run-time dependency of gl wasn't found. Are you using a forked version of mesa? If not, try rebuilding mesa then trying again. And if you are, try using the upstream version.

Also I have the same warning when I compile libepoxy, where is says that the option is unknown. I'll drop this from the build script

So, I made a mistake, I tried to compile libepoxy with mesa from kisslinux/repo and not ehawkvu/kiss-xorg. After compile mesa from ehawkvu/kiss-xorg, I compiled libepoxy successfully. I couldn't find a way to keep two repositories with packages with the same names, like mesa. What is your recommendation for this kind of issue? If you know a way to point out what directory is "kiss build mesa" is using, please tell me.

[echawk]

KISS_PATH works how your system path works; it searches for packages in the first entry, then the second, etc.

To get the mesa package from the kiss-xorg repo, you need to be sure the xorg repos come before upstreams. It should look like this:

KISS_PATH=/path/to/repo/core
KISS_PATH=$KISS_PATH:/path/to/kiss-xorg/extra
KISS_PATH=$KISS_PATH:/path/to/kiss-xorg/xorg
KISS_PATH=$KISS_PATH:/path/to/repo/extra

I personally do this in /etc/profile.d/kiss_path.sh, as it gets sourced on login. If you want to validate that it works, run kiss s mesa and if the first result is from kiss-xorg, then you're set.

[jason123santa]

It compiles fine if I set this repo to be used first.

[alnmy]

I’m having this issue and I have everything setup as it should be
Here’s my /etc/profile
https://termbin.com/iccz
Logs from trying to install libepoxy
https://termbin.com/3icca
Logs from kiss search mesa and libepoxy
https://termbin.com/0xmvk
Any help appreciated

[jason123santa]

@Alanxyz You have to put the core repo before everything else. Then the xorg repo next. That is what worked for me.

[alnmy]

did that and rebuilt mesa
new profile:
https://termbin.com/p2bi
kiss s mesa:
https://termbin.com/z7vm
libepoxy logs:
https://termbin.com/htr1

Tried recompiling system too, but nothing seems to help. Could me using gkisslinux be related? https://github.com/gkisslinux/grepo

[NoSequel]

I seem to be running into the same issue with grepo, not sure whether it's related to grepo or not.

[echawk]

@NoSequel Can you post logs? I don't know why this would fail on glibc, since there are no musl specific fixes in either mesa or libepoxy.

[NoSequel]

@NoSequel Can you post logs? I don't know why this would fail on glibc, since there are no musl specific fixes in either mesa or libepoxy.

Yeah, I'll reply with the logs in just a second.

[NoSequel]

@NoSequel Can you post logs? I don't know why this would fail on glibc, since there are no musl specific fixes in either mesa or libepoxy.

kiss b libepoxy: https://termbin.com/t672

[NoSequel]

@NoSequel Can you post logs? I don't know why this would fail on glibc, since there are no musl specific fixes in either mesa or libepoxy.

kiss b libepoxy: https://termbin.com/t672

Removing libglvnd seems to have fixed the compilation errors with libepoxy, everything compiled perfectly fine after doing so.

[NoSequel]

@NoSequel Can you post logs? I don't know why this would fail on glibc, since there are no musl specific fixes in either mesa or libepoxy.

kiss b libepoxy: https://termbin.com/t672

Removing libglvnd seems to have fixed the compilation errors with libepoxy, everything compiled perfectly fine after doing so.

Sorry for yet another reply, but seemingly NVIDIA proprietary drivers depend on libglvnd. I can't boot into xorg, due to the following error:
https://termbin.com/hr5q

[echawk]

Are the nvidia packages wayland specific? The arch mesa package has libglvnd as a dep so it may just be a config option in the libglvnd package.

[NoSequel]

Are the nvidia packages wayland specific? The arch mesa package has libglvnd as a dep so it may just be a config option in the libglvnd package.

It seems like I had to remove -Dx11=disabled from the libglvnd build file, mesa and libepoxy seem to be compiling now. However, my Xorg error persists - lsmod | grep nvidia returns https://termbin.com/vrnd.

Is this output correct? Could there be something I'm doing wrong?

[NoSequel]

Are the nvidia packages wayland specific? The arch mesa package has libglvnd as a dep so it may just be a config option in the libglvnd package.

It seems like I had to remove -Dx11=disabled from the libglvnd build file, mesa and libepoxy seem to be compiling now. However, my Xorg error persists - lsmod | grep nvidia returns https://termbin.com/vrnd.

Is this output correct? Could there be something I'm doing wrong?

Issue was related to gkiss' NVIDIA build. The issue should be resolved on the newest commit.

kiss-community/grepo#27

[alnmy]

great to hear, might try again gkiss+kiss-xorg again soon