XFree86 4.4 - an attempt on upgrading ports

Dejan Lesjak dejan.lesjak at ijs.si
Fri Apr 16 08:33:22 PDT 2004


On Friday 16 of April 2004 16:20, Tilman Linneweh wrote:
> I tried the ati/radeon driver, in case it has something todo with this.
Well, according to thread starting here:
http://www.mail-archive.com/xfree86%40xfree86.org/msg14618.html
it would seem that this could be driver dependant. I have nvidia here so I'll 
see if I get same error. Right now I'm recompiling the world though.

> BTW, I uploaded an updated tarball of your changes to
> http://people.freebsd.org/~arved/stuff/xfree44-ports.tar.gz
>
> With the following changes:
>
> * Jung-uk Kim <jkim at niksun.com>:
> - patch to build the XServer on AMD64
>
> * arved:
> - Build shared libXau (for AMD64)
> - Remove LATEST_LINK from imake, (there is only one left)
>
> * michael johnson <ahze at ahze.net> PR: 65277
> - make imake respect CC, CXX, CPP
>
> You might want to add this to your CVS Repository.
I did, and I also removed files/patch-Imake.cf from libraries port and from 
Server Makefile. I don't know why this patch didn't fail to apply as the 
changes from this patch are already in source, but as far as I can see it was 
a no-op even when applied.
BTW, does the cvsweb interface help in any way, should I rearange stuff like 
they are in your tarball (ie devel/imake-4 instead of just imake-4)? Also 
feel free to kick me if I made some mistake while incorporating patches..

Furthermore there are now XFree86-4-NestServer, XFree86-4-PrintServer and 
XFree86-4-VirtualFramebufferServer. The trouble here is that file
lib/X11/xserver/SecurityPolicy
is listed in Server, NestServer and VirtualFramebufferServer so I wander what 
would be best way to deal with this.

Dejan


More information about the freebsd-x11 mailing list