Hello Paul, I am compiling natively in DOS. But I also tried it in an MSYS bash shell session and I had almost exactly the same problem (probably to get the same as you with Cygwin, I should have used a version of ant specifically compiled for MSYS, but I used the native Windows ant under MSYS, which explains what happened).
For the patch, I attached to this mail a gzipped tar containing build.xml => the original file from CVS build.xml.new => my patch build.xml.diff => which I got by: diff build.xml build.xml.new > build.xml.diff Regards, Vincent. PS: I had not yet time to check whether the result of installation is workable. Anyhow, there were elisp byte-compile error. Maybe I need to load jde before compiling. I keep you aware when I get a change to try again to debug something. > From: [email protected] > Date: Thu, 20 Aug 2009 23:31:20 -0500 > To: [email protected] > CC: [email protected]; [email protected]; > [email protected]; [email protected] > Subject: Re: [jdee-users] jdb filter cannot interpret line numbers >= 1000 > > Thanks for your sleuthing, Vincent! Anyway you can provide a patch > for the fix? If so, I'll run it and test it. > > Also, are you compiling this under cygwin or dos? On windows, I use > cygwin, which might explain why I'm not getting it. > > Vincent Belaïche writes: > > Dear Paul and al, > > > > I answer to myself because I have located and corrected what is going > > wrong. Ant is not to blame. The problem is in the build.el file that is > > generated when building the configure-ebuild target. > > > > When you replace @{build.lisp.dir} by ${build.lisp.dir} and > > @{src.lisp.dir} by ${src.lisp.dir} then there are \ in a Lisp string > > without escape. This is what causes the problem. > > > > This does not happen for @{cedet.dir}, because it is read directly from > > the build.properties file. > > > > I propose to correct this by replacing \ to / by using some pathconvert > > task like this: > > > > <pathconvert property="unix.build.lisp.dir" targetos="unix"> > > <path path="${build.lisp.dir}"/> > > <mapper> > > <globmapper from="*" to="*"/> > > </mapper> > > </pathconvert> > > > > And then use ${unix.build.lisp.dir} instead of ${build.lisp.dir} in the > > configure-ebuild target replacement. > > > > I have attached a corrected build.xml. With this correction I can go > > further, but there are still errors in the byte-compilation, please see log > > file byte-compile.log.gz > > > > Best regards, > > Vincent. > > > > > -- > Paul Landes > [email protected]
build.xml.tgz
Description: Binary data
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ jdee-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-users
