This nmae collision has been fixed just by renaming CF_MOUNT_RO. This should have no effect on disks behaviour
M On Mon, 2005-08-08 at 17:13 +0200, Erik ten Napel wrote: > Hi, > > Next problem is probably caused by a bug in CFEngine. > I already posted this problem at help-cfengine@gnu.org (CFEngine compile > error @ Cygwin). > > I did install CFEngine 2.1.15 on CygWin 1.5.18-1 > When I did compile the source, it generated next error during the 'make' > step: > > cf.extern.h:272: error: 'MOUNT_RO' redeclared as different kind of symbol > /usr/include/sys/mount.h:34: error: previous definition of 'MOUNT_RO' was > here > > The next page on a CygWin site shows a change in /sys/mount.h: > http://www.mail-archive.com/cygwin-cvs@cygwin.com/msg02981.html > > Possible they changed it to a different datatype then CFEngine expects. > /sys/mount.h contains: > MOUNT_RO = 0x1000 > > globals.c contains: > PRIVATE flag MOUNT_RO = false > > I renamed all MOUNT_RO occurances in the CFEngine source in etn_MOUNT_RO. > CFEngine compiled without problems. But now the 'disks' class returns a > freespace of 0 bytes on all disks. > > Possibly a better sollution has to be found... > > > > > _______________________________________________ > Bug-cfengine mailing list > Bug-cfengine@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-cfengine _______________________________________________ Bug-cfengine mailing list Bug-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cfengine
