On 13/07/2011 11:48 AM, Peter Stuge wrote:
Andrew Leech wrote:
Again just a release tarball issue, but the tarball from above doesn't work
properly, it needs bootstrap run to get jimtcl etc
In particular for a release it's really really important that the two
separate packages (OpenOCD and jimtcl) are *two separate packages*.
The tricks that autobuild jimtcl are convenient for random perusal
but does not very nice packaging make.
From a user perspective, I find the automatically handled jimtcl
compiling to be of enormous benefit. I know there have been huge debates
in the area already though, so don't want to go into it too much, but
the current system does make compiling (for new users) far easier.
specify the full mingw gcc name as per below or CC="gcc-3 -mno-cygwin"
(which I haven't tested recently):
Using: $ ./configure --enable-maintainer-mode --enable-ft2232_ftd2xx
--with-ftd2xx-win32-zipdir=../ftdi CC="i686-pc-mingw32-gcc"
CC should basically *never* be used. --host=i686-pc-mingw32 should be
given to configure in this case, with no environment variables.
Thanks for that, I guess I did know that's what --host does, I'd just forgotten
in this context. For what it's worth I recompiled after a reconfigure with
--host=i686-pc-mingw32 and got a working openocd.exe :-D
I also had problems with jimtcl and dos line ends, the configure
scripts and autosetup files didn't work
Nod. For unknown reason at least configure absolutely must have LF
only line endings.
The problems I was getting appeared to be / problems, ie it was stuffing
up directory paths. I didn't chase down the original source of them
though...
Could bootstrap have it's git commands for pulling jimtcl changed
to ensure it doesn't save in dos mode?
Rather difficult. Unsure how that would be done if at all. What could
be done is to add eol=lf in .gitattributes for the files that need it.
Or at least make a mention of this in the README.Win32 (and possibly in
HACKING as well) as something to watch out for, and how to rectify it.
Debugging a lpc3131 (ARM926EJ-S) with a ft2232 jtagkey compatible
dongle then works fine!
Thanks for writing up the build issues and testing!
Thanks for the feedback!
Andrew
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
