Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
mesa-9.2.5 fails, egl_gallium/llvm related
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2773
Location: Gainesville, Florida

PostPosted: Wed Feb 05, 2014 8:01 pm    Post subject: mesa-9.2.5 fails, egl_gallium/llvm related Reply with quote

I'm suddenly catching this bug on ~amd64, which also prevents glamor and xf86-video-ati from being updated.
https://bugs.gentoo.org/show_bug.cgi?id=481316

Code:
 lLLVMCore -lLLVMSupport -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/lib -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/crtendS.o /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../lib64/crtn.o  -march=amdfam10 -O2 -Wl,--no-undefined -Wl,--allow-multiple-definition -Wl,-O1   -pthread -Wl,-soname -Wl,egl_gallium.so -o .libs/egl_gallium.so
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x6a7): undefined reference to `setupterm'
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x6d0): undefined reference to `tigetnum'
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x6d9): undefined reference to `set_curterm'
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x6e1): undefined reference to `del_curterm'
collect2: error: ld returned 1 exit status
Makefile:849: recipe for target 'egl_gallium.la' failed
gmake[3]: *** [egl_gallium.la] Error 1
gmake[3]: Leaving directory '/var/tmp/portage/media-libs/mesa-9.2.5/work/Mesa-9.2.5-amd64/src/gallium/targets/egl-static'
Makefile:575: recipe for target 'all-recursive' failed
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory '/var/tmp/portage/media-libs/mesa-9.2.5/work/Mesa-9.2.5-amd64/src/gallium/targets'
Makefile:552: recipe for target 'all-recursive' failed
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory '/var/tmp/portage/media-libs/mesa-9.2.5/work/Mesa-9.2.5-amd64/src'
Makefile:603: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
 * ERROR: media-libs/mesa-9.2.5::gentoo failed (compile phase):
 *   emake failed 


Do we need to just wait till it's fixed , or for mesa-10.x.x to reach ~arch, or is there currently a known workaround that actually doesnt' cause other problems?


More info here: https://bugs.gentoo.org/show_bug.cgi?id=488216#c27

The other bug report suggests lists building llvm[-ncurses] as a workaround, but is that wise? Any unforeseen more serious problems trying that?
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
papu
Guru
Guru


Joined: 25 Jan 2008
Posts: 390
Location: Sota algun pi de l'empordà

PostPosted: Sat Feb 08, 2014 2:48 pm    Post subject: Reply with quote

same error for me, but with sys-devel/llvm -ncurses on llvm-3.4 , mesa don't crash , i am using =media-libs/mesa-10.0.3 on package.unmask right now

:?
_________________
--Intel i5 3570k --Asrock z77 ext. 4 --Skill 32GB dd3 --Radeon r9 270 --S.O Gentoo & Win 64bits
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2773
Location: Gainesville, Florida

PostPosted: Sat Feb 08, 2014 8:41 pm    Post subject: Reply with quote

papu,
Thanks for the feedback. :)
I went ahead and did llvm with -ncurses, and then mesa-9.2.5 along with glamor and xf86-video-ati-7.3.0 also emerged with no problems.

This was on one of my ~x86 Gentoo partitions. My~amd64 installs seemed to have sorted themselves out on their own. :roll:

BTW, how is your mesa-10.0.3 unmask working out- any problems appear? I'm assuming you're running ~Arch and not stable, correct?
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
papu
Guru
Guru


Joined: 25 Jan 2008
Posts: 390
Location: Sota algun pi de l'empordà

PostPosted: Sat Feb 08, 2014 9:12 pm    Post subject: Reply with quote

yes i am using unstable, i have not problems so far, i am using glamor and xf86-video-ati also, with 3.13.2 gentoo-sources

http://forums.gentoo.org/viewtopic-p-5863358.html#5863358

i am sorry for my english :oops:
_________________
--Intel i5 3570k --Asrock z77 ext. 4 --Skill 32GB dd3 --Radeon r9 270 --S.O Gentoo & Win 64bits
Back to top
View user's profile Send private message
blietaer
Tux's lil' helper
Tux's lil' helper


Joined: 27 Apr 2006
Posts: 103

PostPosted: Wed Feb 26, 2014 10:03 am    Post subject: Reply with quote

Exactly same issue here....

Code:
-Wl,egl_gallium.so -o .libs/egl_gallium.so
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x5f7): undefined reference to `setupterm'
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x620): undefined reference to `tigetnum'
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x629): undefined reference to `set_curterm'
/usr/lib64/libLLVMSupport.a(Process.o): In function `llvm::sys::Process::FileDescriptorHasColors(int)':
(.text+0x631): undefined reference to `del_curterm'
collect2: error: ld returned 1 exit status
Makefile:849: recipe for target 'egl_gallium.la' failed
gmake[3]: *** [egl_gallium.la] Error 1
gmake[3]: Leaving directory '/var/tmp/portage/media-libs/mesa-9.2.5-r1/work/Mesa-9.2.5-amd64/src/gallium/targets/egl-static'
Makefile:575: recipe for target 'all-recursive' failed
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory '/var/tmp/portage/media-libs/mesa-9.2.5-r1/work/Mesa-9.2.5-amd64/src/gallium/targets'
Makefile:552: recipe for target 'all-recursive' failed
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory '/var/tmp/portage/media-libs/mesa-9.2.5-r1/work/Mesa-9.2.5-amd64/src'
Makefile:603: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
 * ERROR: media-libs/mesa-9.2.5-r1::gentoo failed (compile phase):



I'll give a try to
sys-devel/llvm -ncurses
in packages.use

keep you posted..
Back to top
View user's profile Send private message
ExecutorElassus
l33t
l33t


Joined: 11 Mar 2004
Posts: 765
Location: Stuttgart, Germany

PostPosted: Wed Feb 26, 2014 8:38 pm    Post subject: Reply with quote

I'm on ~amd64. This solution (llvm with -ncurses) did not solve the issue for me. I get a bunch of this:
Code:
.libs/egl.o: In function `create_drm_screen':
egl.c:(.text+0x73): undefined reference to `_eglLog'
egl.c:(.text+0x147): undefined reference to `_eglLog'
egl.c:(.text+0x1f8): undefined reference to `_eglLog'
egl.c:(.text+0x222): undefined reference to `_eglLog'
egl.c:(.text+0x269): undefined reference to `_eglLog'
.libs/egl.o:egl.c:(.text+0x291): more undefined references to `_eglLog' follow
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `egl_g3d_show_screen_surface':
egl_g3d_api.c:(.text+0x1b4): undefined reference to `_eglError'
egl_g3d_api.c:(.text+0x1d2): undefined reference to `_eglError'
egl_g3d_api.c:(.text+0x202): undefined reference to `_eglError'
egl_g3d_api.c:(.text+0x222): undefined reference to `_eglError'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `egl_g3d_copy_buffers':
egl_g3d_api.c:(.text+0x2e6): undefined reference to `_eglGetCurrentContext'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `create_pbuffer_surface':
egl_g3d_api.c:(.text+0x3cc): undefined reference to `_eglInitSurface'
egl_g3d_api.c:(.text+0x450): undefined reference to `_eglError'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `egl_g3d_bind_tex_image':
egl_g3d_api.c:(.text+0x4c6): undefined reference to `_eglGetAPIContext'
egl_g3d_api.c:(.text+0x4e6): undefined reference to `_eglError'
egl_g3d_api.c:(.text+0x5e2): undefined reference to `_eglError'
egl_g3d_api.c:(.text+0x60a): undefined reference to `_eglError'
egl_g3d_api.c:(.text+0x63a): undefined reference to `_eglError'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `egl_g3d_choose_config':
egl_g3d_api.c:(.text+0x694): undefined reference to `_eglParseConfigAttribList'
egl_g3d_api.c:(.text+0x6fa): undefined reference to `_eglFilterConfigArray'
egl_g3d_api.c:(.text+0x75b): undefined reference to `_eglError'
egl_g3d_api.c:(.text+0x77a): undefined reference to `_eglError'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `egl_g3d_compare_config':
egl_g3d_api.c:(.text+0x7bf): undefined reference to `_eglCompareConfigs'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `egl_g3d_match_config':
egl_g3d_api.c:(.text+0x828): undefined reference to `_eglMatchConfig'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `swap_buffers.isra.3':
egl_g3d_api.c:(.text+0x85f): undefined reference to `_eglGetCurrentContext'
../../../../src/gallium/state_trackers/egl/.libs/libegl.a(egl_g3d_api.o): In function `egl_g3d_post_sub_buffer':
but perhaps that's a different issue?

Cheers,

EE
Back to top
View user's profile Send private message
chithanh
Developer
Developer


Joined: 05 Aug 2006
Posts: 1678
Location: Berlin, Germany

PostPosted: Thu Feb 27, 2014 2:46 am    Post subject: Reply with quote

The eglLog error is probably bug 501328 and not related to the OP's issue.

The reason why many ~arch users run into the llvm-3.4[ncurses] issue is that they built mesa-9.2.5 against llvm-3.3 which is no problem, but now build mesa-9.2.5-r1 against llvm-3.4 which fails. Unfortunately there is no good solution how to address this in mesa at this time.
Back to top
View user's profile Send private message
blietaer
Tux's lil' helper
Tux's lil' helper


Joined: 27 Apr 2006
Posts: 103

PostPosted: Thu Feb 27, 2014 8:45 am    Post subject: Reply with quote

llvm -ncurses did the trick for me!
Back to top
View user's profile Send private message
ExecutorElassus
l33t
l33t


Joined: 11 Mar 2004
Posts: 765
Location: Stuttgart, Germany

PostPosted: Thu Feb 27, 2014 9:12 am    Post subject: Reply with quote

chithanh, you are correct: the egLog thing was separate. But, as per that bugreport, building mesa with USE="llvm-shared-libs -llvm" seems to solve the issue.

Cheers,

EE
Back to top
View user's profile Send private message
OPelerin
Guru
Guru


Joined: 17 Jul 2004
Posts: 334
Location: Belgium

PostPosted: Thu Feb 27, 2014 11:54 am    Post subject: Reply with quote

Thanks for the tip!
_________________
Olivier PELERIN
Back to top
View user's profile Send private message
cfgauss
Guru
Guru


Joined: 18 May 2005
Posts: 337
Location: USA

PostPosted: Sat Mar 01, 2014 4:51 pm    Post subject: Reply with quote

ExecutorElassus wrote:
But, as per that bugreport, building mesa with USE="llvm-shared-libs -llvm" seems to solve the issue.

This worked for me. Should this be permanent, in package.use, for future emerges of mesa?
Back to top
View user's profile Send private message
Utsuho Reiuji
n00b
n00b


Joined: 03 Apr 2013
Posts: 55

PostPosted: Sun Mar 02, 2014 12:47 pm    Post subject: Reply with quote

Using
Code:
USE="llvm-shared-libs -llvm" emerge -av --oneshot mesa

worked for me (btw, I'm using ~arch).

I'd also like to know if those use-flags might be required for future mesa updates.
Back to top
View user's profile Send private message
prffzc
Tux's lil' helper
Tux's lil' helper


Joined: 22 Sep 2005
Posts: 94

PostPosted: Tue Mar 04, 2014 1:10 pm    Post subject: Reply with quote

Worked for me too. (using ~amd64)

Thanks!
Back to top
View user's profile Send private message
vibrion
n00b
n00b


Joined: 13 Apr 2006
Posts: 9

PostPosted: Fri Mar 07, 2014 11:27 pm    Post subject: mesa+llvm Reply with quote

Works for me too :D
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2773
Location: Gainesville, Florida

PostPosted: Sat Mar 08, 2014 12:09 pm    Post subject: Reply with quote

So the current consensus for those running ~Arch is to put

Code:
>=media-libs/mesa-9.2.5  llvm-shared-libs -llvm


in /etc/portage/package.use?

I'm wondering why having support for llvm-shared-libs, and then disabling support for llvm itself is somehow a solution for fixing a mesa compiling failure? :?

EDIT: Just synced, and saw this: :)
Code:
[ebuild     U  ] media-libs/mesa-10.1.0 [9.2.5-r1] USE="classic egl gallium gbm llvm llvm-shared-libs nptl -bindist -debug -gles1 -gles2 -opencl -openvg -osmesa -pax_kernel -pic -r600-llvm-compiler (-selinux) -vdpau -wayland -xa -xvmc (-xorg%)" ABI_X86="(64) -32 (-x32)" VIDEO_CARDS="radeon (-freedreno) -i915 -i965 -ilo -intel -nouveau -r100 -r200 -r300 -r600 -radeonsi -vmware" 6,747 kB


llvm and llvm-shared-libs both are enabled. Maybe all this is resolved with mesa-10.1. Will find out soon, I guess.

OK- compiled fine- seems to be working normally.
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum