>>>>    I have not seen the
>>>> problem with fls() that you describe above.  Under what 
>>>> circumstances do
>>>> you see that?
>>> Just a normal build (as above): cd tigervnc-1.0.0/unix&&  ./configure&&
>>> make
>>> Not sure how to build from svn as there is no "./configure" script in
>>> there and automake barfs at me with all sorts of errors on osx.
>>> How do you create a full release tigervnc-X.X.X.tar from an svn tree?
>> In the 1.0 branch, you do
>> cd unix
>> autoreconf -fiv
>> configure {configure arguments}
>> make
>> in trunk, you leave out the 'cd unix' part.  The trunk also has
>> convenience scripts under release/ that you can use.
trunk and 1.0.0 can now build fine, I had to patch this file though (for 

--- a/unix/xorg/libdrm-2.4.0/shared-core/drm.h    2010-01-12 
15:04:21.000000000 -0500
+++ b/unix/xorg/libdrm-2.4.0/shared-core/drm.h    2010-01-12 
15:04:30.000000000 -0500
@@ -79,7 +79,7 @@
  #define DRM_IOC_WRITE        _IOC_WRITE
  #define DRM_IOC(dir, group, nr, size) _IOC(dir, group, nr, size)
-#elif defined(__FreeBSD__) || defined(__FreeBSD_kernel__) || 
defined(__NetBSD__) || defined(__OpenBSD__) || defined(__DragonFly__)
  #include <sys/ioccom.h>
  #define DRM_IOCTL_NR(n)        ((n) & 0xff)
  #define DRM_IOC_VOID        IOC_VOID
Xelabos-Mac-Pro-2:shared-core MacAdmin$ pwd

To avoid this error:
  gcc -DHAVE_CONFIG_H -I. -I../shared-core -g -O2 -MT xf86drm.lo -MD -MP 
-MF .deps/xf86drm.Tpo -c xf86drm.c  -fno-common -DPIC -o .libs/xf86drm.o
xf86drm.c: In function 'drmCommandRead':
xf86drm.c:2311: error: 'DRM_IOC_READ' undeclared (first use in this 
xf86drm.c:2311: error: (Each undeclared identifier is reported only once
xf86drm.c:2311: error: for each function it appears in.)
xf86drm.c: In function 'drmCommandWrite':
xf86drm.c:2340: error: 'DRM_IOC_WRITE' undeclared (first use in this 
xf86drm.c: In function 'drmCommandWriteRead':
xf86drm.c:2369: error: 'DRM_IOC_READ' undeclared (first use in this 
xf86drm.c:2369: error: 'DRM_IOC_WRITE' undeclared (first use in this 
make[3]: *** [xf86drm.lo] Error 1

It wouldn't be too hard to hook up a patch phase into the build scripts, 
but it may not be worth it as the new libdrm releases should have some 
form of darwin/osx support included in the future surely?


This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
Tigervnc-devel mailing list

Reply via email to