Hi! >> A quick workaround is to set the system clock to a time before 2004. > Or to use a 64-bit architecture (yielding max_int = 2^63-1). You are right, using a 64-bit architecture is, of course, also a workaround but I have to stick to my 32-bit system :-(
>> I think this issue can be fixed either by not using OCaml's native >> int for representing merger pragma constants or by changing cilly to >> use smaller numbers than the actual unix timestamp. I'm not sure >> which solution would be preferable or if there are better ones. > I think the former is preferable, but not sure either. I never use the merger > and I am not very familiar with this part of CIL. I'm not familiar with the merger either. I just tried to use it on the 2.6.18 Linux kernel. Unfortunately, cilly seems to be incompatible with the kernel build chain. The merger pragma thing was just the first issue i noticed. Another way to fix the issue on 32-bit may also be to comment out the pragma directive since it's only used by cilly for bookkeeping -- as far as i can tell. If the pragma is not needed by CIL, commenting it out may be a good way to avoid the issue. Cheers, Oliver ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ CIL-users mailing list CIL-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cil-users
