On Mon, 2010-03-15 at 14:30 +0100, Luca Barbieri wrote:
> Adding both -Wl,--no-undefined and -lGL (in
> src/gallium/winsys/drm/Makefile.template) seems to work for me.
>
> The driver loader is already loading libGL.so.1 with RTLD_NOW |
> RTLD_GLOBAL, so I think that the DRI driver depending on li
On Mon, Mar 15, 2010 at 2:30 PM, Luca Barbieri wrote:
> Adding both -Wl,--no-undefined and -lGL (in
> src/gallium/winsys/drm/Makefile.template) seems to work for me.
>
Oh great, that works for me too !
--
Download Intel®
Adding both -Wl,--no-undefined and -lGL (in
src/gallium/winsys/drm/Makefile.template) seems to work for me.
The driver loader is already loading libGL.so.1 with RTLD_NOW |
RTLD_GLOBAL, so I think that the DRI driver depending on libGL.so.1
shouldn't introduce any issue.
--
2010/3/15 Michel Dänzer :
>
> One problem is that drivers can be loaded from several paths; if the HW
> driver fails to load from the first path but succeeds from the next one,
> any error messages from the first attempt would be confusing.
>
If it fails to load because it does not exist ? Or beca
On Mon, 2010-03-15 at 00:09 +0100, Xavier Chantry wrote:
> 14:47 < lb1> the fact is that if you remove a function from mesa .c file,
> everything will succeed, but the resulting driver will fail to
> load
> 14:47 < lb1> because it cannot resolve that symbol
> 14:48 < lb1> not sure wh
On Mon, Mar 15, 2010 at 1:18 AM, tom fogal wrote:
> Xavier Chantry writes:
>> /bin/sh ../../../../../bin/mklib -o swrast_dri.so -noprefix -linker
>> 'gcc' -ldflags '-Wl,--no-allow-shlib-undefined' \
>> ../../common/driverfuncs.o ../common/utils.o swrast.o swrast_sp
>> an.o
>> ../..
Xavier Chantry writes:
> On Mon, Mar 15, 2010 at 12:41 AM, tom fogal wrote:
> >
> > You can emulate the [undefined link errors] by building with
> > -Wl,--no-undefined (or maybe -no-undefined, something like that,
> > see ld(1)).
>
> With -Wl,--no-undefined, I get so many errors that it did not f
On Mon, Mar 15, 2010 at 12:41 AM, tom fogal wrote:
>
> That's just the default compiler/linker setup on Linux. This is in
> contrast to, say, OS X, where undefined symbols cause link errors.
>
> You can emulate the above by building with -Wl,--no-undefined (or maybe
> -no-undefined, something lik
Xavier Chantry writes:
> 14:47 < lb1> the fact is that if you remove a function from mesa .c file,
> everything will succeed, but the resulting driver will fail to l
> oad
> 14:47 < lb1> because it cannot resolve that symbol
> 14:48 < lb1> not sure why
> 14:48 < lb1> I suppose even fo
14:47 < lb1> the fact is that if you remove a function from mesa .c file,
everything will succeed, but the resulting driver will fail to load
14:47 < lb1> because it cannot resolve that symbol
14:48 < lb1> not sure why
14:48 < lb1> I suppose even for shared libraries gcc/ld should fail
10 matches
Mail list logo
