Hi Piet,
I am given to understand by a MacOS X (10.3.6)
user that neither the MACOS nor the TARGET_OS_MAC
macros are being defined during a normal cvs
configure and build operation which makes the
VMS_filename_classes symbol become unresolved due
to the last patch to system.h
It appears that USE_VMS_FILENAMES may be a
reasonable macro to use as an alternative to
choose between VMS and MacOS X filesysstems.
Could you verify that this patch would work for
you?
Thank you,
-- Mark
Index: system.h
===================================================================
RCS file: /cvsroot/cvs/ccvs/lib/system.h,v
retrieving revision 1.81
diff -u -p -u -p -r1.81 system.h
--- system.h 9 Nov 2005 10:59:21 -0000 1.81
+++ system.h 14 Nov 2005 19:47:22 -0000
@@ -284,12 +284,12 @@ extern unsigned char WNT_filename_classe
* WOE32 needs its own class since \ and C:\ style absolute paths also need
* to be accounted for.
*/
-# if defined(MACOS) || defined(TARGET_OS_MAC)
-# define FOLD_FN_CHAR(c) (OSX_filename_classes[(unsigned char) (c)])
-extern unsigned char OSX_filename_classes[];
-# else
+# if defined(USE_VMS_FILENAMES)
# define FOLD_FN_CHAR(c) (VMS_filename_classes[(unsigned char) (c)])
extern unsigned char VMS_filename_classes[];
+# else
+# define FOLD_FN_CHAR(c) (OSX_filename_classes[(unsigned char) (c)])
+extern unsigned char OSX_filename_classes[];
# endif
# endif /* __CYGWIN32__ || WOE32 */
_______________________________________________
Bug-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/bug-cvs
