../../../../src/util/.libs/libmesautil.a(libmesautil_la-build_id.o): In function `build_id_length':
src/util/build_id.c:126: multiple definition of `build_id_length'
../../../../src/mesa/.libs/libmesagallium.a(libmesautil_la-build_id.o):src/util/build_id.c:126: first defined here
could you, please, specify your build-configuration?
I don't see such output.
(In reply to Sergii Romantsov from comment #1)
> could you, please, specify your build-configuration?
./autogen.sh --disable-dri --disable-egl --disable-gbm --enable-debug --with-dri-drivers=swrast --with-gallium-drivers=swrast --with-platforms=x11
I'm seeing similar issues.
$ ../autogen.sh CFLAGS="-g -O0" CXXFLAGS="-g -O0" --enable-debug --enable-xlib-glx --disable-driglx-direct --disable-dri --with-gallium-drivers=swrast,svga --disable-gbm --disable-egl
results in a lot of multiply-defined symbols.
This has probably been happening for the past week or so. I haven't had any time to investigate though.
Vinson, perhaps you could bisect it if you have time.
This seems to be auto tools specific, I cn't replicate with the closest meson configuration I could come up with (-Dbuildtype=debug -Dglx=gallium-xlib -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=swrast,svga -Dgbm=false -Degl=false); meson doesn't have a toggle to turn off direct glx or tls, so it could be related to that.
8396043f304bb2a752130230055605c5c966e89f is the first bad commit
Author: Dylan Baker <email@example.com>
Date: Tue Aug 21 09:46:46 2018 -0700
Replace uses of _mesa_bitcount with util_bitcount
and _mesa_bitcount_64 with util_bitcount_64. This fixes a build problem
in nir for platforms that don't have popcount or popcountll, such as
v2: - Fix additional uses of _mesa_bitcount added after this was
Acked-by: Eric Engestrom <firstname.lastname@example.org> (v1)
Acked-by: Eric Anholt <email@example.com>
Reviewed-by: Ian Romanick <firstname.lastname@example.org>
:040000 040000 9b4d3f30a8c2cb4d4a549b92c6db3cf499338579 dcad5de2d7a236b4fe35516fde4abf5d24516415 M src
bisect run success
Proposed patch: https://patchwork.freedesktop.org/patch/249831/
This should be fixed now.