search for: cygw

...les ... OK * checking examples ... OK * checking PDF version of manual ... OK WARNING: There were 2 warnings, see 'D:/my pkg/linmod.Rcheck/00check.log' for details I don?t know if it is possible to run R CMD build linmod even though I have two warning. But if I do it, I get the following cygwin warning: cygwin warning: MS-DOS style path detected: D:/mypkg/linmod_1.0.tar Preferred POSIX equivalent is: /cygdrive/d/mypkg/linmod_1.0.tar CYGWIN environment variable option ?nodosfilewarning? turns off this warning. Consult the user?s guide for more details about POSIX paths: http://cygwin.co...

Since we are fast approaching the 10th, I thought it appropriate to report this "bug" with the build despite not having worked around it. Build environment is *Summary:* When building llvm-gcc with a arm-apple-darwin target on i686-pc-cygwin, make fails because child calls to configure have an errant semicolon that causes the --srcdir parameter to be ignored by the configure script. This causes the builds in the host-i686-pc-cygwin directory to fail unnecessarily. Removing said semicolon from the configure calls and running 'ma...

...ertime, but if we're using a lot of the operating system interface (any operating system interface), we're doing something wrong. > That said, the architectural issues should still be addressed. I agree. Chris made a good point in that there shouldn't be anything wrong with using cygwin for the build tools but compiling our libraries so that they make use of native windows calls rather than requiring the slow cygwin.dll. That would make our tools work much better on windows and it would not be terribly difficult to do. > What > does LLVM expect to keep in /etc/llvm and whe...