Breaks every time on linking tests/dummy/libGLX_dummy Reproducible: Always I didn't update it since spring, so it's probably not some recent change that breaks it
Created attachment 659358 [details] build.log
Created attachment 659360 [details] emerge --info
That's strange, while configuring for abi_x86_32 your log is using "gcc" instead of well.. "x86_64-pc-linux-gnu-gcc -m32" and reporting x86_64 for both. Unable to reproduce on my end, don't know what is causing this but I "doubt" it has much to do with this package directly and there's something interfering.
Thanks for the pointer, looks like overriding CC drops -m32 for some reason. But can it not?
(In reply to bfg from comment #4) > Thanks for the pointer, looks like overriding CC drops -m32 for some > reason. But can it not? Was just an observation to help point in the right direction, setting CC is not the solution. Someone more involved with how meson/multilib/eclass do things may know what's happening already but meanwhile perhaps providing this file could help: /var/tmp/portage/media-libs/libglvnd-1.3.2/temp/environment
Created attachment 659372 [details] environment
Your emerge --info was showing that CC/CXX weren't set, but in your environment they are set. I also see other things that really shouldn't be set such as BUILD_CC=gcc, if I do `BUILD_CC=gcc emerge -1 libglvnd` I can reproduce your issue. Are you using some kind of special configuration system from those overlays, or setting these things through package.env?
(In reply to Ionen Wolkens from comment #7) > Your emerge --info was showing that CC/CXX weren't set, but in your > environment they are set. I also see other things that really shouldn't be > set such as BUILD_CC=gcc, if I do `BUILD_CC=gcc emerge -1 libglvnd` I can > reproduce your issue. > > Are you using some kind of special configuration system from those overlays, > or setting these things through package.env? Yes, CC and BUILD_CC are set in bashrc
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
