Subject: Re: GLXPixmaps and glXMakeCurrent().
To: Richard Rauch <rkr@olib.org>
From: Tyler Retzlaff <rtr@twentynine.org>
List: tech-x11
Date: 03/23/2004 01:32:57
On Monday 22 March 2004 12:19, Richard Rauch wrote:
> > xsrc builds a loadable XFree86 X server by default there should be no
> > real difference between this and an XFree86 built from xfree86 "raw"
> > sources.
>
> Well, there *is* a very real difference:

> Building via "build.sh" produces a server that does nothing but
> abort.

build.sh only really supports the loadable version of the XFree86 currently so 
given the fact that no loadable server works (native or otherwise) it's not 
surprising the build.sh one doesn't work either.  I have a lot of changes in 
my tree to build a non-loadable version for a while now but I haven't really 
had the enthusiasm to clean it up enough to commit it.

> Building via "make" produces a server with no "modules", and which
> works.

I see, so the native build defaults to non-loadable on amd64 I would guess 
this is because their loader doesn't work with amd64 yet.  Makes sense now.

> The build.sh build was crashing in module-load, apparently; when
> I posted about that to current-users, someone told me that it
> was likely caused by modules (I hadn't come to that conclusion, but
> he said that his X also crashed the same way on AMD64; apparently
> this is a known problem), and that if I built a static linked
> server, it would be okay.  He said that all that I needed to do
> was directly use the Makefile in xsrc.

Yep, sounds sane.

> Whatever the *intention*, directly using the Makefile in xsrc is
> very different in effect than using build.sh in src.

Until loadable works for amd64 or I commit non-loadable reachover build.sh 
won't be an option.

> Is there a CVS tag for this in the NetBSD repository?  Or do I
> need to grab a 4.4 tarball/CVS directly from the XFree86 people?

You would need source from the xfree86 project, if you wanted to bring an 
existing tree up to date you could just cvs up -d -P -r xf-4_4_0.  This is 
still a useful thing to do since it will tell us if our xsrc or xfree86's as 
well that suffers from the problem.

> I'll give this a try in a day or so.  Thanks for the help.  (^&