using dlloader, I get consistent frustrations such as the one in
bug #377 and now this new one.
http://bugs.xfree.org/show_bug.cgi?id=1120 on xfree's bugzilla
shows what some people are doing to get dlloader to work.
Loading dependencies by hand, fun.
This time around:
radeon_drv.so wants gRADEONEntityIndex in ati_drv.so
ati_drv.so wants ATIPreInit in atimisc_drv.so
atimisc_drv.so wants ATIMemoryTypeNames_88800CX in ati_drv.so
Read back those last two. Either everything that ati and
radeon need should go in atimisc, or atimisc and ati should
be collapsed into ati (since ati_drv.so is actually used as
http://bugs.gentoo.org/show_bug.cgi?id=43177 on the Gentoo
Bugzilla shows just why I don't use the elfloader.
This. . . . is annoying.
Currently the elf loader is not supported for loading driver modules.
I assume that the problem with the circular dependecies can get resolved
by using lazy bindings and only resolve symbols when used.
Anyway, this will be dealt with when support for shared driver objects is added.
Currently this is not considered a bug as the feature that would require action is
not in yet.
I think you mean the 'dlloader' is not supported. I wish this silly poorly
designed 'elfloader' was not supported. Anyway this could be fully
supported if you wanted to as we Gentoo & the PaX Teams have tracked
down and sometimes patched every single problem with the existing
codebase when trying to do use dlloader.
Free free to contact myself or the PaX Team if you need help in fixing
the existing codebase.
Note 1: lazy bindings are for code not data.
Note 2: I think this bug should be reopened.
reopening, this is valid.
this is fixed in debrix; i'm taking it to remind myself to merge the fixes back
closing. mostly fixed in CVS, except for one or two issues i'll hit tonight.