Re: Commenced update to XFree86(tm) 4.5.0 on MirOS BSD

On Tue, Mar 22, 2005 at 07:46:17AM +0000, Thorsten Glaser wrote:
>David Dawes dixit:
>
>>First of all, thanks for the continued support!
>
>Sure thing, XFree86 has provided us with a stable X implementation
>long enough, no reason to fix what ain't broke.
>
>>What is the policy there for bumping shared library majors?
>
>ABI changes.
>
>When they introduced ProPolice, all libraries needed some new
>functions from a newer libc major, so they bumped everything.

Oh, OK.

>>The majors
>>for OpenBSD builds of XFree86 are already different than for most other
>>platforms, and I think that was done for the a.out->elf transition.
>
>I don't think they have changed any shared library version when
>i386 went ELF. Shared library versions are machine-independent
>on OpenBSD (and so on MirOS, but we've still not yet sparc and
>macppc running again due to lack of ressources, but it will come).

In OpenBSDLib.tmpl the versions are bumped for releases >= 3.1.  Was that
the ProPolice bump or something else?

>>It might be a good idea to see what of the ws* stuff needs to be folded in.
>
>And some of the other MirOS support code as well, maybe?

Yes, definitely.

>I'm sure I haven't done everything according to XFree86 coding
>standards, but I've tried so far. Especially the MirBSD.cf could
>need some cleaning, because I've had issues when I started. (All
>MirOS BSD versions define __OpenBSD__ *and* __MirBSD__)
>
>I've also linked freetype against the system libz and exported the
>functions, as well as the ProPolice functions, using the xf86 loader,
>so the modules need not be built with -fno-stack-protector any more.

OK.

>The complete diff can be retrieved using
>$ CVS_RSH=ssh cvs -z9 -d [email protected]:/cvs \
>  rdiff -urxf-4_5_0 X11/xc
>(password anoncvs)
>
>(attention, there are three new programmes in xc/programs/,
> namely ssh-askpass, xlock and xsystrace, thus the "diff"
> is a bit large)
>
>On request, I can try to sort out these diffs, but most of it
>is legacy from the OpenBSD version of XF86 4.3 and 4.4RC2
>before they went to x.org, and Matthieu Herrb can probably
>tell you better which purpose a specific patch has for these.
>
>>I haven't seen this on any of the platforms I've tested on, including
>>fairly recent OpenBSD versions.  Do other clients start up OK?  You may
>
>I will try xlock, I think it's got some GLX modes too.

I'm curious because it seems to fail before getting into the GLX-specific
code.

David