Doug Hunt wrote:
>
> Chris:
>
> I suspect major mods to TriD should be put off.
>
> I attach output from xdpyinfo and glxinfo from
> my FC3, i386 linux box that had problems with
> the opengl.t tests. For now I'm just turning off
> WITH_3D on all my systems.

Thanks for the xdpyinfo output below.  For whatever
reason, your GLX support for that X server is not
there i.e. no openGL therefore opengl.t won't run
so all tests will not pass.

A bit more research on the topic and I like the idea
of making the WITH_3D build decision more
conservative: if xdpyinfo does not show GLX as
present then we would skip the build.

Unfortunately, the TriD build decision process is
messy and confusing.  I don't want to whip
something up quick but broken since things seem
to be stablizing nicely for a final 2.4.3 release
check candidate---everything including the
version number set to the release value for last
check testing---next Monday.

Thanks for the testing.

--Chris

> Regards,
>    Doug
>
> [EMAIL PROTECTED]
> Software Engineer III
> UCAR - COSMIC, Tel. (303) 497-2611
>
> On Thu, 10 Aug 2006, Chris Marshall wrote:
>
> > It would be very useful to have the report
> > from the xdpyinfo command on the display that
> > the t/opengl.t failed. I've been trying to
> > come up with a way to failsafe the opengl
> > test without skipping opengl altogether.
> > Unfortunately, every way I turn the answer may
> > be that cleanup/rework of the TriD(OpenGL)
> > stuff planned *post*2.4.3.
> >
> > Oh well.
> >
> > Good night,
> > Chris

> xdpyinfo output:
> ...
> snip
> ...
> number of extensions:    3
> BIG-REQUESTS
> LBX
> XC-MISC
> ...
> snip
> ...
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to