Marek Olšák writes:
> On Thu, Aug 5, 2010 at 8:00 PM, tom fogal wrote:
>
> > tom fogal writes:
> > > git://people.freedesktop.org/~tfogal/mesa
> > > http://cgit.freedesktop.org/~tfogal/mesa/log/?h=7.8
> > >
> > &
Alex Deucher writes:
> On Thu, Aug 5, 2010 at 3:45 PM, tom fogal wrote:
> >> > > Â git://people.freedesktop.org/~tfogal/mesa
> >> > > Â http://cgit.freedesktop.org/~tfogal/mesa/log/?h=7.8
>
> Can you revert 66ad60399ae005084ad8c07569a1c9a461c39ec9?
>
"Kevin H. Hobbs" writes:
> On 08/04/2010 05:58 PM, tom fogal wrote:
> > If you can find the commit that started the trouble (using git
> > bisect), that might shed some light.
>
> With my script adjusted to only report when the test started
&
Brian Paul writes:
[snip]
> My other hunch is something is duplicated in the libOSMesa and libGL
> libraries that's causing things to blow up in general.
This is a good hunch.
I don't know how closely you've been following the thread, Brian, but
previously I brought up how it was important that
"Kevin H. Hobbs" writes:
> On 08/05/2010 06:30 PM, tom fogal wrote:
> > Is your test multithreaded, by any chance?
>
> I can't really answer this : it's VTK's test.
>
> When I run the test in gdb it tells me :
>
> [Thread debugging using
"Kevin H. Hobbs" writes:
> On 08/05/2010 07:07 PM, tom fogal wrote:
> > Brian Paul writes:
> >> My other hunch is something is duplicated in the libOSMesa and libGL
> >> libraries that's causing things to blow up in general.
> >>
> &g
tom fogal writes:
> tom fogal writes:
> > the branch is at:
> >
> > git://people.freedesktop.org/~tfogal/mesa
> > http://cgit.freedesktop.org/~tfogal/mesa/log/?h=7.8
>
> I'd like to push this to 'origin' tomorrow, if there are no
> complai
"Kevin H. Hobbs" writes:
> On 08/06/2010 03:15 PM, tom fogal wrote:
> > If you could build VTK with just a single GL library -- i.e. with
> > just libOSMesa or just libGL, but not both -- and could reproduce
> > the crash,= that would rule out my symbol collision
"Kevin H. Hobbs" writes:
> On 08/10/2010 02:47 PM, Kevin H. Hobbs wrote:
> With VTK_USE_X:BOOL=OFF the test also passes with libGL.so and
> libOSMesa.so switched that is
>
> VTK_USE_X:BOOL=OFF
> OPENGL_gl_LIBRARY:FILEPATH=/home/kevin/mesa/lib/libOSMesa.so
> OSMESA_LIBRARY:FILEPATH=/home/kevin/mes
"Kevin H. Hobbs" writes:
> When I do :
>
> ./autogen.sh --with-driver=xlib --disable-gallium --enable-debug
>
> I get for example :
>
> $ nm lib/libGL.so | grep glDepthFunc
> 0020ce30 T glDepthFunc
> $ nm lib/libOSMesa.so | grep glDepthFunc
> 001ca760 T glDepthFunc
>
> As I und
Dan Nicholson writes:
[snip]
> So, sorry for not reading the whole thread, but is GL being linked
> because it's needed by the app, because pkg-config said so, or
> because the linker added it?
It's needed by the app. Not really, it's not used at runtime, but
needed at link time because the app
"Kevin H. Hobbs" writes:
> On 08/11/2010 05:18 PM, tom fogal wrote:
> > Right. This is exactly why Mesa's name mangling exists.
> > You mean you haven't been mangling this whole time? I guess I haven't
> > been reading these mails closely enough.
&
Dan Nicholson writes:
[snip]
> A possible compromise here would be to put glX* stubs in OSMesa, but
> _that_ seems perverse, too.
That would be wonderful for us, though ;)
Can we go the other way? Put OSMesa symbols in libGL?
That feels an iota less gross to me. Still, some day I'd like to pa
Luca Barbieri writes:
> I just discovered that Microsoft wisely decided to use their own
> calling convention on Win64...
>
> This hasn't actually been tested on Win64 though.
Does mingw or cygwin support win64? I don't know if it's just MS that
uses a new calling convention, or all win64 code,
#x27;t actually rely on any such functionality, so this
is going to be okay for us.
Acked-by: Tom Fogal
Thanks,
-tom
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
101 - 115 of 115 matches
Mail list logo
