On Sun, Jun 06, 2010 at 11:51:43AM +0100, Dr. David Kirkby wrote: > On 06/ 6/10 11:27 AM, Willem Jan Palenstijn wrote: >> The way this usually works is that packages are shipped with the output of >> flex, so that flex doesn't have to be run again if the user doesn't have it. >> >> In this case that also seems to be the case, since the singular package >> includes src/Singular/libparse.cc. However, it's one second older than >> libparse.l. A 'touch src/Singular/libparse.cc' in the spkg-install should >> work >> around this, I think. >> >> -Willem Jan >> > > Thanks, I'll give that a try. > > I can't understand in that case how Singular can possibly install on any > operating system which does not have 'flex' installed. But Mike is saying > Singular builds OK on Cygwin, despite the fact flex is not installed. How > can that be? > > I'm using an old version of GNU make (3.80, dated 2002). Perhaps more > recent versions ignore very small time differences. I could see this > could be dangerous, but I'm also aware that if systems are not properly > synced in time, and use shared file systems, files can appear to have a > date in the future. It may be that certain versions of make take this > into account, and ignore small differences. This does not seem a very > plausible explanation, but I can't think of a better one!
Yeah, I was thinking the same thing. FAT32 only has a timestamp resolution of 2 seconds IIRC, so if the files are on FAT32, that might also be the reason. Or possibly make on cygwin has a greater time tolerance because of this FAT32 property, even when running on other filesystems. -Willem Jan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
