Arrgh... more path issues?

Ted Neward ted at
Sat Mar 28 07:02:40 UTC 2009

Let me guess: this is because the jar utility doesn't like Cygwin paths.?


(cd  C:/Prg/jdk1.7.0/build-fastdebug/classes && C:/Prg/jdk1.6.0/bin/jar xf


uild-fastdebug/tmp/java/plugs/jmf.clist -J-client -J-Xmx383m -J-Xms128m

rmSize=32m -J-XX:MaxPermSize=160m )

lib\rt-closed.jar (The system cannot find the path specified)

        at Method)





make[5]: *** [import-binary-plug-jmf-classes] Error 1

make[5]: Leaving directory


make[4]: *** [all] Error 1



I would suggest, as an RFE or bug, that the various macros used on Windows
have some kind of naming convention to them to indicate where a Cygwin path
is needed, where an MS-style path is needed, and where it makes no
difference. (But I have no offhand suggestions as to what that naming
convention would look like, or how it might interact with the build macros
for other platforms.) There's just GOT to be some kind of way to tell these
apart, though. :-/


Ted Neward | Principal Consultant, ThoughtWorks

Java, .NET, XML Services

Consulting, Teaching, Speaking, Writing

 <> |



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the build-dev mailing list