Re: [Openocd-development] cygwin libtool: s/ECHO=/echo=/

2009-06-09 Thread Gene Smith
Zach Welch wrote: > On Tue, 2009-06-09 at 11:05 -0400, Gene Smith wrote: >> Zach Welch wrote: >>> On Tue, 2009-06-09 at 09:58 -0400, Gene Smith wrote: I think most of the problem I discovered building under cygwin have been addressed today. However, I still have the problem with trunk/li

Re: [Openocd-development] cygwin libtool: s/ECHO=/echo=/

2009-06-09 Thread Zach Welch
On Tue, 2009-06-09 at 11:05 -0400, Gene Smith wrote: > Zach Welch wrote: > > On Tue, 2009-06-09 at 09:58 -0400, Gene Smith wrote: > >> I think most of the problem I discovered building under cygwin have been > >> addressed today. However, I still have the problem with trunk/libtool > >> needing t

Re: [Openocd-development] cygwin libtool: s/ECHO=/echo=/

2009-06-09 Thread Gene Smith
Zach Welch wrote: > On Tue, 2009-06-09 at 09:58 -0400, Gene Smith wrote: >> I think most of the problem I discovered building under cygwin have been >> addressed today. However, I still have the problem with trunk/libtool >> needing to be modified manually to change ECHO= to echo=. Seems to be

Re: [Openocd-development] cygwin libtool: s/ECHO=/echo=/

2009-06-09 Thread Zach Welch
On Tue, 2009-06-09 at 09:58 -0400, Gene Smith wrote: > I think most of the problem I discovered building under cygwin have been > addressed today. However, I still have the problem with trunk/libtool > needing to be modified manually to change ECHO= to echo=. Seems to be > OK in linux. It appea

[Openocd-development] cygwin libtool: s/ECHO=/echo=/

2009-06-09 Thread Gene Smith
I think most of the problem I discovered building under cygwin have been addressed today. However, I still have the problem with trunk/libtool needing to be modified manually to change ECHO= to echo=. Seems to be OK in linux. It appears to be a mismatch between the libtool version on my linux