Re: xvfb not built on vax and x68k?
David Brownlee <[email protected]> Tue, 3 Feb 2009 23:21:28 +0000 (GMT)
| Newsgroups | gmane.os.netbsd.ports.x68k,gmane.os.netbsd.devel.x11,gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <alpine.NEB.2.00.0902032313420.1239@localhost> |
On Tue, 3 Feb 2009, Patrick Finnegan wrote: > On Tuesday 03 February 2009, Brad Parker wrote: >> David Brownlee wrote: >>> any >>> objections to making those two ports consistent with all >>> the others so all NetBSD ports build the Xvfb virtual >>> framebuffer X server? >> >> If it balloons out the build times I'd prefer not, at least on the >> vax port. None of the vaxen I use have frame buffers. > > Well, I think the point of xvfb is that it doesn't require or use a > framebuffer in the machine. Yup, exactly. The relative additional time for a build with and without xvb is going to be marginal - if you want to save build time you should skip building X11 altogether, or crossbuild from a faster box. Given that x68k is going to have xvfb added that would leave vax as the odd port out. I'll time three vax builds - one without x11, one with x11 but no xvfb, and one with x11 and xvfb. These will all be crossbuilds from a random x86 box, but as its relative times we're looking at that should be fine. (I think its important that vax should be able to build natively, but I'd prefer this thread not to sidetrack onto that issue, and if you must, please drop the non port-vax addresses from the cc) -- David/absolute -- www.NetBSD.org: No hype required --