Re: cygwin problem in building in deep directories

2012-05-14 Thread Lubos Lunak
On Monday 14 of May 2012, Noel Grandin wrote: > On 2012-05-14 15:33, Lubos Lunak wrote: > > It shouldn't be make, when I built a small testapp that just printed > > out its argv[], everything looked ok to me. To me it looks like the > > limit is there either when converting args between cygwin and

Re: cygwin problem in building in deep directories

2012-05-14 Thread Noel Grandin
On 2012-05-14 15:33, Lubos Lunak wrote: It shouldn't be make, when I built a small testapp that just printed out its argv[], everything looked ok to me. To me it looks like the limit is there either when converting args between cygwin and pure-MS apps (or whatever it is that happens at that p

Re: cygwin problem in building in deep directories

2012-05-14 Thread Noel Grandin
On 2012-05-14 15:23, Matúš Kukan wrote: Me neither, it may also be bug in make or whatever. Oh, I could do that If I wanted, but I was hoping (with a little assistance) to track down some of the bugs in long path handling so it didn't bite as many newcomers. Any ideas? For example, is the

Re: cygwin problem in building in deep directories

2012-05-14 Thread Lubos Lunak
On Monday 14 of May 2012, Matúš Kukan wrote: > On 14 May 2012 13:46, Noel Grandin wrote: > > After that, I start getting errors in SW and SC that look like (see > > below). The weird thing is that if I cut and paste the command line into > > a separate script and execute, it runs fine. > > This is

Re: cygwin problem in building in deep directories

2012-05-14 Thread Matúš Kukan
On 14 May 2012 13:46, Noel Grandin wrote: > After that, I start getting errors in SW and SC that look like (see below). > The weird thing is that if I cut and paste the command line into a separate > script and execute, it runs fine. This is exactly what Lubos was experiencing and he chose to use

Re: cygwin problem in building in deep directories

2012-05-14 Thread Noel Grandin
On 2012-05-14 13:13, Michael Stahl wrote: in general you are right, configure clearly shouldn't create empty paths in case of error, so i've changed the PathFormat on master to report errors. Thanks for the fix. After that, I start getting errors in SW and SC that look like (see below). The

Re: cygwin problem in building in deep directories

2012-05-14 Thread Michael Meeks
On Mon, 2012-05-14 at 11:04 +0200, Noel Grandin wrote: > OK, so as it turns out this is entirely my fault. I have this in my > configure :-) > --with-solver-and-workdir-root=/cygdrive/D/reallyreallylong/reallyreallylong/reallyreallylong > which was generating this warning during aut

Re: cygwin problem in building in deep directories

2012-05-14 Thread Michael Stahl
On 14/05/12 11:04, Noel Grandin wrote: > > > On 2012-05-14 10:50, Matúš Kukan wrote: >> No, It should be -Fo$W/... and $W is empty. Why ? You can set WORKDIR >> manually in config_host.mk if it is empty there. > > OK, so as it turns out this is entirely my fault. I have this in my > configure

Re: cygwin problem in building in deep directories

2012-05-14 Thread Noel Grandin
On 2012-05-14 10:50, Matúš Kukan wrote: No, It should be -Fo$W/... and $W is empty. Why ? You can set WORKDIR manually in config_host.mk if it is empty there. OK, so as it turns out this is entirely my fault. I have this in my configure --with-solver-and-workdir-root=/cygdrive/D/really

Re: cygwin problem in building in deep directories

2012-05-14 Thread Matúš Kukan
On 14 May 2012 10:25, Noel Grandin wrote: > Hi > > OK, So I tracked this down a bit more. > I moved my libo directory to a very deep location and rebuilt. > It failed in the xml2cmp module. > Notice the last few lines of this error - it looks like our makefile messed > something up because the "-F

cygwin problem in building in deep directories

2012-05-14 Thread Noel Grandin
Hi OK, So I tracked this down a bit more. I moved my libo directory to a very deep location and rebuilt. It failed in the xml2cmp module. Notice the last few lines of this error - it looks like our makefile messed something up because the "-F" option has an "o" where it should have a "$O" [ b