931 reputation
31021
bio website
location
age
visits member for 3 years, 3 months
seen Jul 21 '13 at 4:38

Apr
3
comment dlclose does not call library destructors, dlopen called just once
i suggest you to give a closer look to the documentation, just below the dlclose() section: "manpages.ubuntu.com/manpages/hardy/man3/dlopen.3.html "libraries should export routines using the __attribute__((constructor)) and __attribute__((destructor)) function attributes. See the gcc info pages for information on these, Constructor routines are executed before dlopen() returns, and destructor routines are executed before dlclose() returns."
Apr
3
revised dlclose does not call library destructors, dlopen called just once
edited tags
Apr
2
asked dlclose does not call library destructors, dlopen called just once
Dec
31
awarded  Notable Question
Dec
23
revised Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
edited title
Dec
23
comment Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
failure, for some reason this is not working, i've softlinked the whole /usr/include/x86_64-linux-gnu/sys folder to /usr/include/sys, but still getting the same error... no idea what is going on
Dec
21
comment Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
and of course, this situation carries on exactly the same to other distros based on Precise and Quantal, such as Linux Mint 13 and 14.
Dec
21
revised Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
edited title
Dec
21
revised Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
edited title
Dec
21
comment Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
This is such an awfully bad solution, that i would most likely downvote it, if it wasn't for the small fact that it is, with great likelihood, also the best possible solution available, given the known constraints of poor architectural and engineering decisions happening at ubuntu. I wouldn't go as far as upvoting it either. I will leave it sit a while, i will catch my breath tomorrow, or probably the day after, probably kick and punch some stuff at the gym, and after i get my morning coffee, i will accept this answer, unless a better one shows up. Also will ponder on other lines of work.
Dec
20
revised Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
edited title
Dec
20
revised Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
edited title
Dec
20
asked Ubuntu Precise system headers moved somewhere else and sys/ucontext.h cannot be found
Dec
14
comment Video driver under lxc container?
i mean, i can see direct rendering: yes on the host, but that doesn't translate directly to the container, because the system installation (including the fglrx driver) will not be shared with the containers, right? That article seems to point that at least some direct rendering is possible using the open source driver, which is a good fallback plan for me, but if i could rely on the propietary fglrx ati driver it would be golden
Dec
14
comment Video driver under lxc container?
so, the question is: if i run LIBGL_DEBUG=verbose glxinfo | grep rendering inside the lxc container console, will i see "direct rendering: yes"?
Dec
3
asked Video driver under lxc container?
Dec
3
answered indirect rendering issue on 12.04, using ati driver
Dec
3
comment indirect rendering issue on 12.04, using ati driver
i changed the symlink in /usr/lib32/dri to point to the x86_64 library and it doesn't give the warning anymore (i know, weird!) so the only remaining error is the cryptic and unhelpful: libGL: screen 0 does not appear to be DRI2 capable
Dec
3
comment indirect rendering issue on 12.04, using ati driver
ok now glxinfo gives this error: libGL error: dlopen /usr/lib32/dri/swrast_dri.so failed (/usr/lib32/dri/swrast_dri.so: wrong ELF class: ELFCLASS32)
Dec
3
comment indirect rendering issue on 12.04, using ati driver
the library is there! so i just need to make a symlink to the other path..