Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Stroller]

> On 17 Jul 2017, at 03:14, Walter Dnes  wrote:
> 
> On Mon, Jul 17, 2017 at 01:43:46AM +0100, Stroller wrote
>> This system is headless, but I have x11-wm/xpra installed on it so I can run 
>> X11 apps remotely.
>> 
>> Recent emerges of world have been failing at media-libs/mesa
>> ...
>> 
>> All I can make out is that it's a problem with gallium. The current
>> version of mesa appears to have gallium enabled, though.
>> 
>> I know nothing about mesa, not even really what it's for, so I don't
>> know if I should just try disabling gallium and trying again.
> 
>  I've got 17.0.6 building and running fine, under GCC 6.3.0 (YES !),
> without gallium.  I suggest trying "-gallium" in make.conf.  Here's my
> mesa "pretend build" output...
> 
> [ebuild   R] media-libs/mesa-17.0.6::gentoo  USE="bindist classic dri3 
> egl gbm gles2 nptl -d3d9 -debug -gallium -gles1 -llvm -opencl -openmax 
> -osmesa -pax_kernel -pic (-selinux) -vaapi -valgrind -vdpau -vulkan -wayland 
> -xa -xvmc" VIDEO_CARDS="i915 intel (-freedreno) -i965 -imx -nouveau -r100 
> -r200 -r300 -r600 -radeon -radeonsi (-vc4) (-vivante) -vmware" 0 KiB 

llvm depends on gallium, I think, as emerging with USE="-gallium" throws an 
error of that nature. 

Emerging with USE="-gallium -llvm" works, but I was pleased with the solution 
provided by IceAmber, as it allows me to update mesa with the default flags 
(i.e. with those enabled).

Since I don't use X11 much I feel happier using the default flags wherever 
possible (irrational of me, perhaps), unless they pull in too many dependencies.

I appreciate all the help,

Stroller.

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Stroller]

> On 18 Jul 2017, at 02:33, IceAmber  wrote:
> 
> Actually, this is the c++ 11 abi bug, read the news
> And you can solve it by `revdep-rebuild --library 'libstdc++.so.6' -- 
> --exclude gcc`

Many thanks!

That worked perfectly.

Stroller.

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[IceAmber]

Actually, this is the c++ 11 abi bug, read the news

And you can solve it by `revdep-rebuild --library 'libstdc++.so.6' --
--exclude gcc`

On Mon, Jul 17, 2017 at 5:02 PM, Mart Raudsepp  wrote:

> Ühel kenal päeval, E, 17.07.2017 kell 12:00, kirjutas Mart Raudsepp:
> > Ühel kenal päeval, E, 17.07.2017 kell 03:46, kirjutas Rasmus Thomsen:
> > > Hello,
> > >
> > > > undefined reference to
> > >
> > > `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11:
> > > :b
> > > asic_string , std::allocator > const&)'
> > >
> > > Seems to be the error, maybe you have to recompile llvm with c++11
> >
> > And without any VIDEO_CARDS set, you are only getting llvmpipe with
> > USE=llvm. If you don't need that with Xpra, you don't need that (and
> > USE=gallium). I'm not sure if Xpra can make use of it or not, but if
> > GL
> > is sent over the wire or something, then probably not at the server-
> > side.
> > What llvmpipe is is described here:
> > https://www.mesa3d.org/llvmpipe.html
>
> Actually to be fully correct, I believe USE=gallium might build more
> stuff even without any VIDEO_CARDS, e.g some state trackers and
> whatnot, but nothing useful to really make use of it if you don't have
> any VIDEO_CARDS for mesa or any other packages.
>
>
>

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Mart Raudsepp]

Ühel kenal päeval, E, 17.07.2017 kell 12:00, kirjutas Mart Raudsepp:
> Ühel kenal päeval, E, 17.07.2017 kell 03:46, kirjutas Rasmus Thomsen:
> > Hello,
> > 
> > > undefined reference to
> > 
> > `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11:
> > :b
> > asic_string , std::allocator > const&)' 
> > 
> > Seems to be the error, maybe you have to recompile llvm with c++11
> 
> And without any VIDEO_CARDS set, you are only getting llvmpipe with
> USE=llvm. If you don't need that with Xpra, you don't need that (and
> USE=gallium). I'm not sure if Xpra can make use of it or not, but if
> GL
> is sent over the wire or something, then probably not at the server-
> side.
> What llvmpipe is is described here:
> https://www.mesa3d.org/llvmpipe.html

Actually to be fully correct, I believe USE=gallium might build more
stuff even without any VIDEO_CARDS, e.g some state trackers and
whatnot, but nothing useful to really make use of it if you don't have
any VIDEO_CARDS for mesa or any other packages.

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Mart Raudsepp]

Ühel kenal päeval, E, 17.07.2017 kell 03:46, kirjutas Rasmus Thomsen:
> Hello,
> 
> > undefined reference to
> `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11::b
> asic_string , std::allocator > const&)' 
> 
> Seems to be the error, maybe you have to recompile llvm with c++11

And without any VIDEO_CARDS set, you are only getting llvmpipe with
USE=llvm. If you don't need that with Xpra, you don't need that (and
USE=gallium). I'm not sure if Xpra can make use of it or not, but if GL
is sent over the wire or something, then probably not at the server-
side.
What llvmpipe is is described here:
https://www.mesa3d.org/llvmpipe.html

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Rasmus Thomsen]

Hello,

> undefined reference to 
> `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11::basic_string
>  , std::allocator > const&)'

Seems to be the error, maybe you have to recompile llvm with c++11

Regards,
Rasmus

 Original Message 
On 17 Jul 2017, 02:43, Stroller wrote:

> This system is headless, but I have x11-wm/xpra installed on it so I can run 
> X11 apps remotely.
>
> Recent emerges of world have been failing at media-libs/mesa
>
> Currently I have mesa-13.0.5 installed; I have this problem with mesa-17.0.6 
> (current stable) and mesa-17.1.4 (latest in the tree when I tried this a few 
> days ago).
>
> The error says I should post this if I need support:
>
> $ emerge -pqv '=media-libs/mesa-17.0.6::gentoo'
> [ebuild U ] media-libs/mesa-17.0.6 [13.0.5] USE="classic dri3 egl gallium gbm 
> llvm nptl -bindist -d3d9 -debug -gles1 -gles2 -opencl -openmax -osmesa 
> -pax_kernel -pic (-selinux) -vaapi -valgrind -vdpau -vulkan -wayland -xa 
> -xvmc (-gcrypt%) (-libressl%) (-nettle%*) (-openssl%*)" ABI_X86="(64) -32 
> (-x32)" VIDEO_CARDS="(-freedreno) -i915 -i965 -imx% -intel -nouveau -r100 
> -r200 -r300 -r600 -radeon
> -radeonsi (-vc4) (-vivante) -vmware"
> $
>
> The build.log doesn't point me towards any obvious solutions, or maybe I just 
> don't know how to read it.
>
> All I can make out is that it's a problem with gallium. The current version 
> of mesa appears to have gallium enabled, though.
>
> I know nothing about mesa, not even really what it's for, so I don't know if 
> I should just try disabling gallium and trying again.
>
> I'm grateful for any thoughts,
>
> Stroller.
>
> Tail end of /var/tmp/portage/media-libs/mesa-17.0.6/temp/build.log follows:
>
> /bin/sh ../../../../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++ 
> -march=native -O2 -pipe -Wall -fno-math-errno -fno-trapping-math -shared 
> -shrext .so -module -no-undefined -avoid-version -Wl,--gc-sections 
> -Wl,--no-undefined 
> -Wl,--version-script=/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6/src/gallium/targets/dri/dri.sym
>  
> -Wl,--dynamic-list=/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6/src/gallium/targets/dri-vdpau.dyn
>  -L/usr/lib64 -Wl,-O1 -Wl,--as-needed -o gallium_dri.la -rpath /usr/lib64/dri 
> gallium_dri_la-target.lo ../../../../src/mesa/libmesagallium.la 
> ../../../../src/mesa/drivers/dri/common/libdricommon.la 
> ../../../../src/mesa/drivers/dri/common/libmegadriver_stub.la 
> ../../../../src/gallium/state_trackers/dri/libdri.la 
> ../../../../src/gallium/auxiliary/libgalliumvl.la 
> ../../../../src/gallium/auxiliary/libgallium.la 
> ../../../../src/gallium/drivers/ddebug/libddebug.la 
> ../../../../src/gallium/drivers/noop/libnoop.la 
> ../../../../src/gallium/drivers/rbug/librbug.la 
> ../../../../src/gallium/drivers/trace/libtrace.la 
> ../../../../src/mapi/shared-glapi/libglapi.la -lexpat -ldrm -lm -lpthread 
> -ldl -ldrm 
> ../../../../src/gallium/auxiliary/pipe-loader/libpipe_loader_static.la 
> ../../../../src/gallium/winsys/sw/null/libws_null.la 
> ../../../../src/gallium/winsys/sw/wrapper/libwsw.la 
> ../../../../src/gallium/winsys/sw/dri/libswdri.la 
> ../../../../src/gallium/winsys/sw/kms-dri/libswkmsdri.la -ldrm 
> ../../../../src/gallium/drivers/softpipe/libsoftpipe.la 
> ../../../../src/gallium/drivers/llvmpipe/libllvmpipe.la -lLLVMX86Disassembler 
> -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter 
> -lLLVMDebugInfoCodeView -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine 
> -lLLVMInstrumentation -lLLVMTransformUtils -lLLVMX86Desc -lLLVMMCDisassembler 
> -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMMCJIT 
> -lLLVMExecutionEngine -lLLVMTarget -lLLVMRuntimeDyld -lLLVMObject 
> -lLLVMMCParser -lLLVMBitReader -lLLVMMC -lLLVMBitWriter -lLLVMAnalysis 
> -lLLVMProfileData -lLLVMCore -lLLVMSupport
> libtool: link: x86_64-pc-linux-gnu-g++ -fPIC -DPIC -shared -nostdlib 
> /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/../../../../lib64/crti.o 
> /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/crtbeginS.o 
> .libs/gallium_dri_la-target.o -Wl,--whole-archive 
> ../../../../src/mesa/.libs/libmesagallium.a 
> ../../../../src/mesa/drivers/dri/common/.libs/libdricommon.a 
> ../../../../src/mesa/drivers/dri/common/.libs/libmegadriver_stub.a 
> ../../../../src/gallium/state_trackers/dri/.libs/libdri.a 
> ../../../../src/gallium/auxiliary/.libs/libgalliumvl.a 
> ../../../../src/gallium/auxiliary/.libs/libgallium.a 
> ../../../../src/gallium/drivers/ddebug/.libs/libddebug.a 
> ../../../../src/gallium/drivers/noop/.libs/libnoop.a 
> ../../../../src/gallium/drivers/rbug/.libs/librbug.a 
> ../../../../src/gallium/drivers/trace/.libs/libtrace.a 
> ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_static.a 
> ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a 
> ../../../../src/gallium/winsys/sw/wrapper/.libs/libwsw.a 
> ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a 
> 

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Walter Dnes]

On Mon, Jul 17, 2017 at 01:43:46AM +0100, Stroller wrote
> This system is headless, but I have x11-wm/xpra installed on it so I can run 
> X11 apps remotely.
> 
> Recent emerges of world have been failing at media-libs/mesa
> 
> Currently I have mesa-13.0.5 installed; I have this problem with mesa-17.0.6 
> (current stable) and mesa-17.1.4 (latest in the tree when I tried this a few 
> days ago).
> 
> The error says I should post this if I need support:
> 
> $ emerge -pqv '=media-libs/mesa-17.0.6::gentoo'
> [ebuild U ] media-libs/mesa-17.0.6 [13.0.5] USE="classic dri3 egl gallium 
> gbm llvm nptl -bindist -d3d9 -debug -gles1 -gles2 -opencl -openmax -osmesa 
> -pax_kernel -pic (-selinux) -vaapi -valgrind -vdpau -vulkan -wayland -xa 
> -xvmc (-gcrypt%) (-libressl%) (-nettle%*) (-openssl%*)" ABI_X86="(64) -32 
> (-x32)" VIDEO_CARDS="(-freedreno) -i915 -i965 -imx% -intel -nouveau -r100 
> -r200 -r300 -r600 -radeon -radeonsi (-vc4) (-vivante) -vmware"

> The build.log doesn't point me towards any obvious solutions, or
> maybe I just don't know how to read it.
> 
> All I can make out is that it's a problem with gallium. The current
> version of mesa appears to have gallium enabled, though.
> 
> I know nothing about mesa, not even really what it's for, so I don't
> know if I should just try disabling gallium and trying again.

  I've got 17.0.6 building and running fine, under GCC 6.3.0 (YES !),
without gallium.  I suggest trying "-gallium" in make.conf.  Here's my
mesa "pretend build" output...

[ebuild   R] media-libs/mesa-17.0.6::gentoo  USE="bindist classic dri3 egl 
gbm gles2 nptl -d3d9 -debug -gallium -gles1 -llvm -opencl -openmax -osmesa 
-pax_kernel -pic (-selinux) -vaapi -valgrind -vdpau -vulkan -wayland -xa -xvmc" 
VIDEO_CARDS="i915 intel (-freedreno) -i965 -imx -nouveau -r100 -r200 -r300 
-r600 -radeon -radeonsi (-vc4) (-vivante) -vmware" 0 KiB 

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications