Re: [Openocd-development] 0.5.0 MinGW configure failure
On 16 November 2011 23:05, Whitlock, Bradley D wrote: > I believe I have found the issue with one of the previous issues that I do > not believe has been solved yet (see below): > > I thought the issue was resolved - it is for me anyway. Are you building from git master or a release ? Replied to new mailing list aswell - the old one will be closing soon - 31/12/2011 Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
I believe I have found the issue with one of the previous issues that I do not believe has been solved yet (see below): The issue is on line 503 of cc.tcl, the call to 'exec-with-stderr' will not work. I am not familiar with TCL, so I don't know the reasoning behind this, but changing to just 'exec' will allow the configure script to complete, albeit with some extra output to stdout. Regards, Brad >> >> i686-pc-mingw32 >> just installed a fresh copy of msys/mingw - still same error. > > I can reproduce here at a Vista 32bit installation of MinGW/MSys. It is > a myth now that I have the other PC working (XP SP3). I have updated > both MinGW/MSys installation to the latest. > > === configuring in jimtcl (/d/work/openocd/openocd-0.5.0/build_mingw/jimtcl) > configure: running /bin/sh ../../jimtcl/configure.gnu > --disable-option-checking > '--prefix=/usr/local' '--enable-jlink' '--enable-ft2232_libftdi' > --cache-file=/ > dev/null --srcdir=../../jimtcl > No installed jimsh or tclsh, building local bootstrap jimsh0 > The system cannot find the path specified. > ../../jimtcl/autosetup/system.tcl:150: Error: > in procedure 'use' called at file "../../jimtcl/auto.def", line 5 > in procedure 'use' called at file "../../jimtcl/autosetup/cc.tcl", line 29 > in procedure 'config_guess' called at file > "../../jimtcl/autosetup/system.tcl", > line 150 > Try: 'configure --debug' for a full stack trace > configure: error: ../../jimtcl/configure.gnu failed for jimtcl > we are currently working on this issue offlist, hopefully soon resolved. Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 16, 2011 at 6:13 PM, Spencer Oliver wrote: > On 16 August 2011 11:03, Steve Bennett wrote: >> Good news. Spencer and I sorted out the jimtcl build problem on mingw. >> The fix is in the jimtcl git repo. >> See: >> http://repo.or.cz/w/jimtcl.git/commit/645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 >> > > yah - i will update the openocd jim version Thanks now building under MinGW/MSys works fine. Thanks a lot. I also tested with cross 32bit MinGW build under 64bit Ubuntu 11.04 and it works fine as well. If there is going to be a 5.01 release, this should probably be included. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 16 August 2011 11:42, Steve Bennett wrote: > On 16/08/2011, at 8:32 PM, Spencer Oliver wrote: > >> On 16 August 2011 11:13, Spencer Oliver wrote: >>> On 16 August 2011 11:03, Steve Bennett wrote: On 12/08/2011, at 11:12 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 3:39 PM, Xiaofan Chen wrote: >> On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken >> wrote: >>> Hi Xiaofan >>> >>> In my case I struggled with the same problem for a day or two. That >>> is why >>> I need to know if it is the checkout of the version, or the updating of >>> the >>> mingw32 compiler that fixed the problem. >>> >>> After doing the ./bootstrap command, the head revision of JimTCL is >>> cloned >>> from its repository - afaik. Thus, to get version 0.63 checked out do >>> the >>> following >>> cd jimtcl >>> git tag -l (Gives you a list of the tags for the jimtcl repository) >>> git checkout 0.63 >>> >>> The version of Jimtcl in the directory should now be 0.63. To view the >>> tags >>> of the openocd source, and checkout for instance 0.5.0-rc2 the same >>> procedure is used. >>> >>> Hopefully this helps, cause I've been trying to replicate the problem >>> without success for a while now. >>> >> >> This is clear now. I will make sure that my MinGW/Cygwin setup >> are up to date and see if that helps. If not, I will follow your >> suggestion >> and downgrade jimtcl to see if that help. Thanks for the helps! >> > Good news. Spencer and I sorted out the jimtcl build problem on mingw. The fix is in the jimtcl git repo. See: http://repo.or.cz/w/jimtcl.git/commit/645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 Cheers, Steve >>> >>> yah - i will update the openocd jim version >>> >> >> just updated to latest jim master 645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 >> get a jimtcl build error now on cygwin and linux - msys is working fine. >> >> cc -g -O2 -rdynamic -o jimsh jimsh.o _initjimsh.o libjim.a -ldl >> _initjimsh.o: In function `Jim_initjimshInit': >> /home/soliver/openocd/openocd-rel/jimtcl/_initjimsh.c:6: undefined >> reference to `Jim_Eval_Named' >> collect2: ld returned 1 exit status >> make[2]: *** [jimsh] Error 1 > > Is this with a clean tree? > Jim_Eval_Named() is now a macro rather than a function in jim.h > working fine with a clean tree - thanks. Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 16/08/2011, at 8:32 PM, Spencer Oliver wrote: > On 16 August 2011 11:13, Spencer Oliver wrote: >> On 16 August 2011 11:03, Steve Bennett wrote: >>> On 12/08/2011, at 11:12 PM, Xiaofan Chen wrote: >>> On Wed, Aug 10, 2011 at 3:39 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken > wrote: >> Hi Xiaofan >> >> In my case I struggled with the same problem for a day or two. That is >> why >> I need to know if it is the checkout of the version, or the updating of >> the >> mingw32 compiler that fixed the problem. >> >> After doing the ./bootstrap command, the head revision of JimTCL is >> cloned >> from its repository - afaik. Thus, to get version 0.63 checked out do >> the >> following >> cd jimtcl >> git tag -l (Gives you a list of the tags for the jimtcl repository) >> git checkout 0.63 >> >> The version of Jimtcl in the directory should now be 0.63. To view the >> tags >> of the openocd source, and checkout for instance 0.5.0-rc2 the same >> procedure is used. >> >> Hopefully this helps, cause I've been trying to replicate the problem >> without success for a while now. >> > > This is clear now. I will make sure that my MinGW/Cygwin setup > are up to date and see if that helps. If not, I will follow your > suggestion > and downgrade jimtcl to see if that help. Thanks for the helps! > >>> >>> Good news. Spencer and I sorted out the jimtcl build problem on mingw. >>> The fix is in the jimtcl git repo. >>> See: >>> http://repo.or.cz/w/jimtcl.git/commit/645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 >>> >>> Cheers, >>> Steve >>> >> >> yah - i will update the openocd jim version >> > > just updated to latest jim master 645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 > get a jimtcl build error now on cygwin and linux - msys is working fine. > > cc -g -O2 -rdynamic -o jimsh jimsh.o _initjimsh.o libjim.a -ldl > _initjimsh.o: In function `Jim_initjimshInit': > /home/soliver/openocd/openocd-rel/jimtcl/_initjimsh.c:6: undefined > reference to `Jim_Eval_Named' > collect2: ld returned 1 exit status > make[2]: *** [jimsh] Error 1 Is this with a clean tree? Jim_Eval_Named() is now a macro rather than a function in jim.h Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 16 August 2011 11:13, Spencer Oliver wrote: > On 16 August 2011 11:03, Steve Bennett wrote: >> On 12/08/2011, at 11:12 PM, Xiaofan Chen wrote: >> >>> On Wed, Aug 10, 2011 at 3:39 PM, Xiaofan Chen wrote: On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken wrote: > Hi Xiaofan > > In my case I struggled with the same problem for a day or two. That is > why > I need to know if it is the checkout of the version, or the updating of > the > mingw32 compiler that fixed the problem. > > After doing the ./bootstrap command, the head revision of JimTCL is cloned > from its repository - afaik. Thus, to get version 0.63 checked out do the > following > cd jimtcl > git tag -l (Gives you a list of the tags for the jimtcl repository) > git checkout 0.63 > > The version of Jimtcl in the directory should now be 0.63. To view the > tags > of the openocd source, and checkout for instance 0.5.0-rc2 the same > procedure is used. > > Hopefully this helps, cause I've been trying to replicate the problem > without success for a while now. > This is clear now. I will make sure that my MinGW/Cygwin setup are up to date and see if that helps. If not, I will follow your suggestion and downgrade jimtcl to see if that help. Thanks for the helps! >>> >> >> Good news. Spencer and I sorted out the jimtcl build problem on mingw. >> The fix is in the jimtcl git repo. >> See: >> http://repo.or.cz/w/jimtcl.git/commit/645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 >> >> Cheers, >> Steve >> > > yah - i will update the openocd jim version > just updated to latest jim master 645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 get a jimtcl build error now on cygwin and linux - msys is working fine. cc -g -O2 -rdynamic -o jimsh jimsh.o _initjimsh.o libjim.a -ldl _initjimsh.o: In function `Jim_initjimshInit': /home/soliver/openocd/openocd-rel/jimtcl/_initjimsh.c:6: undefined reference to `Jim_Eval_Named' collect2: ld returned 1 exit status make[2]: *** [jimsh] Error 1 Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 16 August 2011 11:03, Steve Bennett wrote: > On 12/08/2011, at 11:12 PM, Xiaofan Chen wrote: > >> On Wed, Aug 10, 2011 at 3:39 PM, Xiaofan Chen wrote: >>> On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken >>> wrote: Hi Xiaofan In my case I struggled with the same problem for a day or two. That is why I need to know if it is the checkout of the version, or the updating of the mingw32 compiler that fixed the problem. After doing the ./bootstrap command, the head revision of JimTCL is cloned from its repository - afaik. Thus, to get version 0.63 checked out do the following cd jimtcl git tag -l (Gives you a list of the tags for the jimtcl repository) git checkout 0.63 The version of Jimtcl in the directory should now be 0.63. To view the tags of the openocd source, and checkout for instance 0.5.0-rc2 the same procedure is used. Hopefully this helps, cause I've been trying to replicate the problem without success for a while now. >>> >>> This is clear now. I will make sure that my MinGW/Cygwin setup >>> are up to date and see if that helps. If not, I will follow your suggestion >>> and downgrade jimtcl to see if that help. Thanks for the helps! >>> >> > > Good news. Spencer and I sorted out the jimtcl build problem on mingw. > The fix is in the jimtcl git repo. > See: > http://repo.or.cz/w/jimtcl.git/commit/645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 > > Cheers, > Steve > yah - i will update the openocd jim version Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 12/08/2011, at 11:12 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 3:39 PM, Xiaofan Chen wrote: >> On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken >> wrote: >>> Hi Xiaofan >>> >>> In my case I struggled with the same problem for a day or two. That is why >>> I need to know if it is the checkout of the version, or the updating of the >>> mingw32 compiler that fixed the problem. >>> >>> After doing the ./bootstrap command, the head revision of JimTCL is cloned >>> from its repository - afaik. Thus, to get version 0.63 checked out do the >>> following >>> cd jimtcl >>> git tag -l (Gives you a list of the tags for the jimtcl repository) >>> git checkout 0.63 >>> >>> The version of Jimtcl in the directory should now be 0.63. To view the tags >>> of the openocd source, and checkout for instance 0.5.0-rc2 the same >>> procedure is used. >>> >>> Hopefully this helps, cause I've been trying to replicate the problem >>> without success for a while now. >>> >> >> This is clear now. I will make sure that my MinGW/Cygwin setup >> are up to date and see if that helps. If not, I will follow your suggestion >> and downgrade jimtcl to see if that help. Thanks for the helps! >> > Good news. Spencer and I sorted out the jimtcl build problem on mingw. The fix is in the jimtcl git repo. See: http://repo.or.cz/w/jimtcl.git/commit/645ed6fd4b6f9038c7e1d85d74c3872b3cb9a507 Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 3:39 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken > wrote: >> Hi Xiaofan >> >> In my case I struggled with the same problem for a day or two. That is why >> I need to know if it is the checkout of the version, or the updating of the >> mingw32 compiler that fixed the problem. >> >> After doing the ./bootstrap command, the head revision of JimTCL is cloned >> from its repository - afaik. Thus, to get version 0.63 checked out do the >> following >> cd jimtcl >> git tag -l (Gives you a list of the tags for the jimtcl repository) >> git checkout 0.63 >> >> The version of Jimtcl in the directory should now be 0.63. To view the tags >> of the openocd source, and checkout for instance 0.5.0-rc2 the same >> procedure is used. >> >> Hopefully this helps, cause I've been trying to replicate the problem >> without success for a while now. >> > > This is clear now. I will make sure that my MinGW/Cygwin setup > are up to date and see if that helps. If not, I will follow your suggestion > and downgrade jimtcl to see if that help. Thanks for the helps! > For my Vista 32bit MinGW setup where the 0.5.0 release does not work, downgrading jimtcl to 0.63 does help -- now it works. There are lots of warnings about jimautoconf.h but in the end it works. ../../../jimtcl/jimautoconf.h:113:0: warning: "PACKAGE_BUGREPORT" redefined ../../../config.h:231:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:116:0: warning: "PACKAGE_NAME" redefined ../../../config.h:234:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:119:0: warning: "PACKAGE_STRING" redefined ../../../config.h:237:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:122:0: warning: "PACKAGE_TARNAME" redefined ../../../config.h:240:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:128:0: warning: "PACKAGE_VERSION" redefined ../../../config.h:246:0: note: this is the location of the previous definition For those who do not use git, you can download the jimtcl 0.63 zip file from github mirror. Replace the jimtcl with this version and then you should be able to build with MinGW. https://github.com/msteveb/jimtcl/zipball/0.63 But I think this is just a temp workaround. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10/08/2011 14:41, Jie Zhang wrote: On Wed, Aug 10, 2011 at 9:29 AM, Xiaofan Chen wrote: On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: Just tested building native windoze under cygwin and working fine here. I used the release tarball and the following configure line: ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 --disable-shared --disable-werror --enable-ft2232_ftd2xx Yes --disable-werror is necessary. If not the following errors will come out. I remember Jie Zheng has some proposals to fix this. ../../../../src/jtag/drivers/ft2232.c: In function 'ft2232_write': ../../../../src/jtag/drivers/ft2232.c:518:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' Yes. And Spencer said he would fix it if he got a chance. Jie http://repo.or.cz/w/openocd/ntfreak.git ftdi Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 9:29 AM, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: >> Just tested building native windoze under cygwin and working fine here. >> I used the release tarball and the following configure line: >> ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 >> --disable-shared --disable-werror --enable-ft2232_ftd2xx >> > > Yes --disable-werror is necessary. If not the following errors > will come out. I remember Jie Zheng has some proposals to > fix this. > > ../../../../src/jtag/drivers/ft2232.c: In function 'ft2232_write': > ../../../../src/jtag/drivers/ft2232.c:518:3: error: format '%u' > expects type 'unsigned int', but argument 6 has type 'FT_STATUS' Yes. And Spencer said he would fix it if he got a chance. Jie ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: > Just tested building native windoze under cygwin and working fine here. > I used the release tarball and the following configure line: > ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 > --disable-shared --disable-werror --enable-ft2232_ftd2xx > Yes --disable-werror is necessary. If not the following errors will come out. I remember Jie Zheng has some proposals to fix this. libtool: compile: i686-pc-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../.. /../src/jtag/drivers -I../../.. -I../../../../src -I../../../src -DPKGDATADIR=\" /usr/local/share/openocd\" -DPKGLIBDIR=\"/usr/local/lib/openocd\" -I../../../../ jimtcl -I../../../jimtcl -g -O2 -D__USE_MINGW_ANSI_STDIO -Wall -Wstrict-prototyp es -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Werror -MT ft2232.lo -MD -MP -MF .deps/ft2232.Tp o -c ../../../../src/jtag/drivers/ft2232.c -o ft2232.o cc1: warnings being treated as errors ../../../../src/jtag/drivers/ft2232.c: In function 'ft2232_write': ../../../../src/jtag/drivers/ft2232.c:518:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c: In function 'ft2232_read': ../../../../src/jtag/drivers/ft2232.c:561:4: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c: In function 'ft2232_init_ftd2xx': ../../../../src/jtag/drivers/ft2232.c:2218:4: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c::3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:2238:5: error: format '%u' expects type 'unsigned int', but argument 6 has type 'DWORD' ../../../../src/jtag/drivers/ft2232.c:2257:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:2268:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:2285:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:2291:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:2297:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:2307:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_DEVICE' ../../../../src/jtag/drivers/ft2232.c:2308:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'DWORD' ../../../../src/jtag/drivers/ft2232.c: In function 'ft2232_purge_ftd2xx': ../../../../src/jtag/drivers/ft2232.c:2322:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c: In function 'signalyzer_h_led_set': ../../../../src/jtag/drivers/ft2232.c:3643:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3651:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3659:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3666:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c: In function 'signalyzer_h_init': ../../../../src/jtag/drivers/ft2232.c:3755:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3765:4: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3779:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3786:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3793:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3801:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3808:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3815:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3822:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3831:3: error: format '%u' expects type 'unsigned int', but argument 6 has type 'FT_STATUS' ../../../../src/jtag/drivers/ft2232.c:3845:5: e
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 6:05 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 5:12 PM, Olivier Schonken > wrote: >> Could you try building with >> >> ../configure --host=i686-pc-mingw32 --enable-jlink --enable-ft2232_libftdi >> in stead of >> >> ../configure --build=i686-pc-mingw32 --enable-jlink --enable-ft2232_libftdi >> >> Afaik, --host specifies the cross-compiler i.e. the target system, while >> --build specifies the system it is being built on - cygwin etc. Remember to >> do a make clean beforehand to clear any old object files. >> >> This might solve the path errors with building JimTCL. > > You are absolutely right. I made a mistake here and I will try again. Yes it works now. Thanks. I also need to make sure that I use fresh build source tree. mcuee@AcerPC /cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cross $ ../configure --host=i686-pc-mingw32 --build=i686-pc-cygwin --enable-jlink --enable-ft2232_libftdi checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for i686-pc-mingw32-strip... i686-pc-mingw32-strip checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for i686-pc-mingw32-gcc... i686-pc-mingw32-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-pc-mingw32-gcc accepts -g... yes checking for i686-pc-mingw32-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of i686-pc-mingw32-gcc... gcc3 checking for i686-pc-mingw32-gcc option to accept ISO C99... -std=gnu99 checking whether i686-pc-mingw32-gcc -std=gnu99 and cc understand -c and -o together... yes checking for i686-pc-mingw32-ranlib... i686-pc-mingw32-ranlib checking build system type... i686-pc-cygwin checking host system type... i686-pc-mingw32 checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by i686-pc-mingw32-gcc -std=gnu99... /usr/i686-pc-mingw32/bin/ld.exe checking if the linker (/usr/i686-pc-mingw32/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/i686-pc-mingw32-nm -B checking the name lister (/usr/bin/i686-pc-mingw32-nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-cygwin file names to i686-pc-mingw32 format... func_convert_file_cygwin_to_w32 checking how to convert i686-pc-cygwin file names to toolchain format... func_convert_file_noop checking for /usr/i686-pc-mingw32/bin/ld.exe option to reload object files... -r checking for i686-pc-mingw32-objdump... i686-pc-mingw32-objdump checking how to recognize dependent libraries... file_magic ^x86 archive import|^x86 DLL checking for i686-pc-mingw32-dlltool... i686-pc-mingw32-dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_implib checking for i686-pc-mingw32-ar... i686-pc-mingw32-ar checking for archiver @FILE support... @ checking for i686-pc-mingw32-strip... (cached) i686-pc-mingw32-strip checking for i686-pc-mingw32-ranlib... (cached) i686-pc-mingw32-ranlib checking command to parse /usr/bin/i686-pc-mingw32-nm -B output from i686-pc-min gw32-gcc -std=gnu99 object... ok checking for sysroot... no checking for i686-pc-mingw32-mt... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... i686-pc-mingw32-gcc -std=gnu99 -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... no checking for objdir... .libs checking if i686-pc-mingw32-gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no checking for i686-pc-mingw32-gcc -std=gnu99 option to produce PIC... -DDLL_EXPORT -DPIC checking if i686-pc-mingw32-gcc -std=gnu99 PIC flag -DDLL_EXPORT -DPIC works... yes checking if i686-pc-mingw32-gcc -std=gnu99 static flag -static works... yes checking if i686-pc-mingw32-gcc -std=gnu99 supports -c -o file.o... yes checking if i686-pc-mingw32-gcc -std=gnu99 supports -c -o file.o... (cached) yes checkin
Re: [Openocd-development] 0.5.0 MinGW configure failure
The problem with jimsh, jimsh0 on MinGW build is probably somewhere in the script chain jimtcl/configure jimtcl/autosetup/find-tclsh jimtcl/autosetup/test-tclsh BTW it will not accept jimsh version lesser than 0.70 as can be seen in test-tclsh script. Best regards Vit ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10 August 2011 13:26, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 11:11 PM, Spencer Oliver wrote: >> On 9 August 2011 16:01, Xiaofan Chen wrote: >>> On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver >>> wrote: >>> Just tested building native windoze under cygwin and working fine here. I used the release tarball and the following configure line: ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 --disable-shared --disable-werror --enable-ft2232_ftd2xx >>> >>> Try build in a separate build directory and see if that is okay >>> or not. >>> >> >> works fine in/out of src tree. >> Just to be sure i also deleted the release src tree between builds. > > This is the key here. It seems to me that jimtcl build is a bit strange > that it creates a jimsh0.exe under the source distribution (jimtcl\autosetup > directory) even though I am building out of source tree. And that > seems to cause problems for subsequent build if I change the build > type. > > You are correct about the location of jimsh0 and it was pointed out to Steve a while back. However i have not seen any issues caused by this under cygwin. Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10 August 2011 13:30, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 6:35 PM, Spencer Oliver wrote: >> On 10 August 2011 11:15, Steve Bennett wrote: for me jimtcl has never built under msys since the update. log is attached below, for info jimsh0.exe is built ok. No installed jimsh or tclsh, building local bootstrap jimsh0 The system cannot find the path specified. autosetup/system.tcl:150: Error: in procedure 'use' called at file "auto.def", line 5 in procedure 'use' called at file "autosetup/cc.tcl", line 29 in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 Try: 'configure --debug' for a full stack trace configure: error: ./configure.gnu failed for jimtcl >>> >>> It is failing while trying to run config.guess. >>> >>> What do you get when you run: >>> >>> sh jimtcl/autosetup/config.guess >>> >> >> i686-pc-mingw32 >> just installed a fresh copy of msys/mingw - still same error. > > I can reproduce here at a Vista 32bit installation of MinGW/MSys. It is > a myth now that I have the other PC working (XP SP3). I have updated > both MinGW/MSys installation to the latest. > > === configuring in jimtcl (/d/work/openocd/openocd-0.5.0/build_mingw/jimtcl) > configure: running /bin/sh ../../jimtcl/configure.gnu > --disable-option-checking > '--prefix=/usr/local' '--enable-jlink' '--enable-ft2232_libftdi' > --cache-file=/ > dev/null --srcdir=../../jimtcl > No installed jimsh or tclsh, building local bootstrap jimsh0 > The system cannot find the path specified. > ../../jimtcl/autosetup/system.tcl:150: Error: > in procedure 'use' called at file "../../jimtcl/auto.def", line 5 > in procedure 'use' called at file "../../jimtcl/autosetup/cc.tcl", line 29 > in procedure 'config_guess' called at file > "../../jimtcl/autosetup/system.tcl", > line 150 > Try: 'configure --debug' for a full stack trace > configure: error: ../../jimtcl/configure.gnu failed for jimtcl > we are currently working on this issue offlist, hopefully soon resolved. Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 6:35 PM, Spencer Oliver wrote: > On 10 August 2011 11:15, Steve Bennett wrote: >>> for me jimtcl has never built under msys since the update. >>> log is attached below, for info jimsh0.exe is built ok. >>> >>> No installed jimsh or tclsh, building local bootstrap jimsh0 >>> The system cannot find the path specified. >>> autosetup/system.tcl:150: Error: >>> in procedure 'use' called at file "auto.def", line 5 >>> in procedure 'use' called at file "autosetup/cc.tcl", line 29 >>> in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 >>> Try: 'configure --debug' for a full stack trace >>> configure: error: ./configure.gnu failed for jimtcl >> >> It is failing while trying to run config.guess. >> >> What do you get when you run: >> >> sh jimtcl/autosetup/config.guess >> > > i686-pc-mingw32 > just installed a fresh copy of msys/mingw - still same error. I can reproduce here at a Vista 32bit installation of MinGW/MSys. It is a myth now that I have the other PC working (XP SP3). I have updated both MinGW/MSys installation to the latest. === configuring in jimtcl (/d/work/openocd/openocd-0.5.0/build_mingw/jimtcl) configure: running /bin/sh ../../jimtcl/configure.gnu --disable-option-checking '--prefix=/usr/local' '--enable-jlink' '--enable-ft2232_libftdi' --cache-file=/ dev/null --srcdir=../../jimtcl No installed jimsh or tclsh, building local bootstrap jimsh0 The system cannot find the path specified. ../../jimtcl/autosetup/system.tcl:150: Error: in procedure 'use' called at file "../../jimtcl/auto.def", line 5 in procedure 'use' called at file "../../jimtcl/autosetup/cc.tcl", line 29 in procedure 'config_guess' called at file "../../jimtcl/autosetup/system.tcl", line 150 Try: 'configure --debug' for a full stack trace configure: error: ../../jimtcl/configure.gnu failed for jimtcl -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 11:11 PM, Spencer Oliver wrote: > On 9 August 2011 16:01, Xiaofan Chen wrote: >> On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: >> >>> Just tested building native windoze under cygwin and working fine here. >>> I used the release tarball and the following configure line: >>> ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 >>> --disable-shared --disable-werror --enable-ft2232_ftd2xx >> >> Try build in a separate build directory and see if that is okay >> or not. >> > > works fine in/out of src tree. > Just to be sure i also deleted the release src tree between builds. This is the key here. It seems to me that jimtcl build is a bit strange that it creates a jimsh0.exe under the source distribution (jimtcl\autosetup directory) even though I am building out of source tree. And that seems to cause problems for subsequent build if I change the build type. mcuee@AcerPC /cygdrive/d/work/openocd/openocd-0.5.0/build_cygwin $ ls -la ../jimtcl/autosetup/jimsh0.exe -rwxr-xr-x+ 1 mcuee None 242820 Aug 10 20:10 ../jimtcl/autosetup/jimsh0.exe mcuee@AcerPC /cygdrive/d/work/openocd/openocd-0.5.0/build_cygwin $ ls -la ./jimtcl/jimsh.exe -rwxr-xr-x+ 1 mcuee None 724407 Aug 10 20:11 ./jimtcl/jimsh.exe My strange problem with the Cygwin native built was caused by this problem. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10 August 2011 11:15, Steve Bennett wrote: > On 10/08/2011, at 6:39 PM, Spencer Oliver wrote: > >> On 10 August 2011 07:11, Steve Bennett wrote: >>> On 10/08/2011, at 3:03 PM, Xiaofan Chen wrote: >>> On Wed, Aug 10, 2011 at 11:44 AM, Steve Bennett wrote: > On 10/08/2011, at 9:43 AM, Xiaofan Chen wrote: >> It was not up to date but very close. Anyway, I just updated it and >> the issue is still there with the release zip file. I will try the git >> tree later. >> >> === configuring in jimtcl >> (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr >> oss/jimtcl) >> configure: running /bin/sh ../../jimtcl/configure.gnu >> --disable-option-checking >> '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' >> '--enable-ft22 >> 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null >> --srcdir=../../ >> jimtcl >> ../../jimtcl/configure: line 3: >> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >> : No such file or directory >> ../../jimtcl/configure: line 3: exec: >> D:/work/openocd/openocd-0.5.0/jimtcl/autos >> : cannot execute: No such file or directory >> configure: error: ../../jimtcl/configure.gnu failed for jimtcl > > You have something weird going on there. Note how the lines are truncated. > For example: > >> ../../jimtcl/configure: line 3: >> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >> : No such file or directory Yes I agree that the error message is quite strange. It is directly copy and paste from the Cygwin prompt. I will check again. The other errors under MinGW are also quite strange. I think I will try another setup. >>> >>> Let us know how that goes. >>> > Or is that your cut and paste of the error messages? > If so, please add the errors as an attachment instead. > > FYI: I build the release tarball on windows/mingw without any problems. Glad to know that. As per the previous answer from Spen that MinGW/Msys is not supported by jimtcl. Is that not true? >>> >>> That is *not* true. >>> The version of jimtcl in openocd-0.5.0 fully supports building on mingw/msys >>> >> >> for me jimtcl has never built under msys since the update. >> log is attached below, for info jimsh0.exe is built ok. >> >> No installed jimsh or tclsh, building local bootstrap jimsh0 >> The system cannot find the path specified. >> autosetup/system.tcl:150: Error: >> in procedure 'use' called at file "auto.def", line 5 >> in procedure 'use' called at file "autosetup/cc.tcl", line 29 >> in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 >> Try: 'configure --debug' for a full stack trace >> configure: error: ./configure.gnu failed for jimtcl > > It is failing while trying to run config.guess. > > What do you get when you run: > > sh jimtcl/autosetup/config.guess > i686-pc-mingw32 just installed a fresh copy of msys/mingw - still same error. Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10/08/2011, at 6:39 PM, Spencer Oliver wrote: > On 10 August 2011 07:11, Steve Bennett wrote: >> On 10/08/2011, at 3:03 PM, Xiaofan Chen wrote: >> >>> On Wed, Aug 10, 2011 at 11:44 AM, Steve Bennett >>> wrote: On 10/08/2011, at 9:43 AM, Xiaofan Chen wrote: > It was not up to date but very close. Anyway, I just updated it and > the issue is still there with the release zip file. I will try the git > tree later. > > === configuring in jimtcl > (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr > oss/jimtcl) > configure: running /bin/sh ../../jimtcl/configure.gnu > --disable-option-checking > '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' > '--enable-ft22 > 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null > --srcdir=../../ > jimtcl > ../../jimtcl/configure: line 3: > D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j > : No such file or directory > ../../jimtcl/configure: line 3: exec: > D:/work/openocd/openocd-0.5.0/jimtcl/autos > : cannot execute: No such file or directory > configure: error: ../../jimtcl/configure.gnu failed for jimtcl You have something weird going on there. Note how the lines are truncated. For example: > ../../jimtcl/configure: line 3: > D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j > : No such file or directory >>> >>> Yes I agree that the error message is quite strange. It is directly copy >>> and paste from the Cygwin prompt. I will check again. >>> >>> The other errors under MinGW are also quite strange. I think I will >>> try another setup. >> >> Let us know how that goes. >> >>> Or is that your cut and paste of the error messages? If so, please add the errors as an attachment instead. FYI: I build the release tarball on windows/mingw without any problems. >>> >>> Glad to know that. As per the previous answer from Spen that >>> MinGW/Msys is not supported by jimtcl. Is that not true? >> >> That is *not* true. >> The version of jimtcl in openocd-0.5.0 fully supports building on mingw/msys >> > > for me jimtcl has never built under msys since the update. > log is attached below, for info jimsh0.exe is built ok. > > No installed jimsh or tclsh, building local bootstrap jimsh0 > The system cannot find the path specified. > autosetup/system.tcl:150: Error: > in procedure 'use' called at file "auto.def", line 5 > in procedure 'use' called at file "autosetup/cc.tcl", line 29 > in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 > Try: 'configure --debug' for a full stack trace > configure: error: ./configure.gnu failed for jimtcl It is failing while trying to run config.guess. What do you get when you run: sh jimtcl/autosetup/config.guess -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 5:12 PM, Olivier Schonken wrote: > Could you try building with > > ../configure --host=i686-pc-mingw32 --enable-jlink --enable-ft2232_libftdi > in stead of > > ../configure --build=i686-pc-mingw32 --enable-jlink --enable-ft2232_libftdi > > Afaik, --host specifies the cross-compiler i.e. the target system, while > --build specifies the system it is being built on - cygwin etc. Remember to > do a make clean beforehand to clear any old object files. > > This might solve the path errors with building JimTCL. You are absolutely right. I made a mistake here and I will try again. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 4:22 PM, Steve Bennett wrote: > On 10/08/2011, at 6:15 PM, Xiaofan Chen wrote: >> But I am happy now since direct MinGW build works and direct Cygwin >> build also works. > > Thanks. That's good enough for me. > Just for those who can not wait for Freddie Chopin's binary, here is a test binary build of OpenOCD-0.5.0. http://code.google.com/p/picusb/downloads/detail?name=openocd_0.5.0_mingw.zip This is a test build of OpenOCD-0.5.0 release under MinGW. YMMV. Take note that OpenOCD is licensed under GPL. The source codes of OpenOCD-0.5.0 can be downloaded from the project website. http://sourceforge.net/projects/openocd/files/openocd/0.5.0/ The build is configured with the following option so that only J-Link and FT2232_libftdi hardware are supported. ../configure --enable-jlink --enable-ft2232_libftdi I also include relevant files for libftdi-0.19 and libusb-win32 1.2.5.0 release. Please refer to the Readme.txt file within the libftdi_libusb-win32 directory. In particular, it talks about driver installation options for FTDI based hardware. * I include this one in the zip file as well. http://code.google.com/p/picusb/downloads/detail?name=libftdi_0.19_devkit_MinGW32_26July2011.zip ** This is for developers who want to use libftdi-0.19 under Windows using MinGW. It includes libusb-win32 (1.2.5.0 release) driver installer from libusb-win32 project. It includes the following. 1) include file for libftdi-0.19 and libusb-win32 2) MinGW 32bit dll for libftdi-0.19 3) MinGW import and static library for libftdi-0.19 4) MinGW 32 bit build of libftdi-0.19 examples. 5) libusb-win32 device driver and filter driver installer which work under 32bit/64bit Windows. System requirements: Windows 2000, XP 32bit/64bit, Vista 32bit/64bit, Windows 7 32bit/64bit. 32bit/64bit Windows 2003/2008/2008R2 should also work. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10 August 2011 07:11, Steve Bennett wrote: > On 10/08/2011, at 3:03 PM, Xiaofan Chen wrote: > >> On Wed, Aug 10, 2011 at 11:44 AM, Steve Bennett >> wrote: >>> On 10/08/2011, at 9:43 AM, Xiaofan Chen wrote: It was not up to date but very close. Anyway, I just updated it and the issue is still there with the release zip file. I will try the git tree later. === configuring in jimtcl (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr oss/jimtcl) configure: running /bin/sh ../../jimtcl/configure.gnu --disable-option-checking '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' '--enable-ft22 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null --srcdir=../../ jimtcl ../../jimtcl/configure: line 3: D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j : No such file or directory ../../jimtcl/configure: line 3: exec: D:/work/openocd/openocd-0.5.0/jimtcl/autos : cannot execute: No such file or directory configure: error: ../../jimtcl/configure.gnu failed for jimtcl >>> >>> You have something weird going on there. Note how the lines are truncated. >>> For example: >>> ../../jimtcl/configure: line 3: D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j : No such file or directory >> >> Yes I agree that the error message is quite strange. It is directly copy >> and paste from the Cygwin prompt. I will check again. >> >> The other errors under MinGW are also quite strange. I think I will >> try another setup. > > Let us know how that goes. > >> >>> Or is that your cut and paste of the error messages? >>> If so, please add the errors as an attachment instead. >>> >>> FYI: I build the release tarball on windows/mingw without any problems. >> >> Glad to know that. As per the previous answer from Spen that >> MinGW/Msys is not supported by jimtcl. Is that not true? > > That is *not* true. > The version of jimtcl in openocd-0.5.0 fully supports building on mingw/msys > for me jimtcl has never built under msys since the update. log is attached below, for info jimsh0.exe is built ok. No installed jimsh or tclsh, building local bootstrap jimsh0 The system cannot find the path specified. autosetup/system.tcl:150: Error: in procedure 'use' called at file "auto.def", line 5 in procedure 'use' called at file "autosetup/cc.tcl", line 29 in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 Try: 'configure --debug' for a full stack trace configure: error: ./configure.gnu failed for jimtcl Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10/08/2011, at 6:15 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 4:11 PM, Xiaofan Chen wrote: >> On Wed, Aug 10, 2011 at 2:11 PM, Steve Bennett >> wrote: >>> On 10/08/2011, at 3:03 PM, Xiaofan Chen wrote: > FYI: I build the release tarball on windows/mingw without any problems. Glad to know that. As per the previous answer from Spen that MinGW/Msys is not supported by jimtcl. Is that not true? >>> >>> That is *not* true. >>> The version of jimtcl in openocd-0.5.0 fully supports building on mingw/msys >>> >> >> Seems this is true and it works without using Cygwin. >> Thanks for the information. > > Cygwin build of 0.5.0 also works in this PC (XP SP3). > > Cross MinGW build under Cygwin (up to date installation of Cygwin) > still fails but with a different error. > > But I am happy now since direct MinGW build works and direct Cygwin > build also works. > Thanks. That's good enough for me. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 4:11 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 2:11 PM, Steve Bennett wrote: >> On 10/08/2011, at 3:03 PM, Xiaofan Chen wrote: FYI: I build the release tarball on windows/mingw without any problems. >>> >>> Glad to know that. As per the previous answer from Spen that >>> MinGW/Msys is not supported by jimtcl. Is that not true? >> >> That is *not* true. >> The version of jimtcl in openocd-0.5.0 fully supports building on mingw/msys >> > > Seems this is true and it works without using Cygwin. > Thanks for the information. Cygwin build of 0.5.0 also works in this PC (XP SP3). Cross MinGW build under Cygwin (up to date installation of Cygwin) still fails but with a different error. But I am happy now since direct MinGW build works and direct Cygwin build also works. bash-4.1# ../configure --build=i686-pc-mingw32 --enable-jlink --enable-ft2232_libftdi checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ISO C99... -std=gnu99 checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for ranlib... ranlib checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc -std=gnu99... /usr/i686-pc-cygwin/bin/ld.exe checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-mingw32 file names to i686-pc-mingw32 format... func_convert_file_msys_to_w32 checking how to convert i686-pc-mingw32 file names to toolchain format... func_c onvert_file_msys_to_w32 checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... file_magic ^x86 archive import| ^x86 DLL checking for dlltool... dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_imp lib checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... (cached) ranlib checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -std=gnu99 -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no checking for gcc -std=gnu99 option to produce PIC... -DDLL_EXPORT -DPIC checking if gcc -std=gnu99 PIC flag -DDLL_EXPORT -DPIC works... yes checking if gcc -std=gnu99 static flag -static works... no checking if gcc -std=gnu99 supports -c -o file.o... yes checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes checking whether the gcc -std=gnu99 linker (/usr/i686-pc-cygwin/bin/ld.exe) supp orts shared libraries... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking for an ANSI C-conforming const... yes checking for long long int... yes checking for library containing ioperm... -lioperm checking for library containing dlopen... none required checking sys/so
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 2:11 PM, Steve Bennett wrote: > On 10/08/2011, at 3:03 PM, Xiaofan Chen wrote: >>> FYI: I build the release tarball on windows/mingw without any problems. >> >> Glad to know that. As per the previous answer from Spen that >> MinGW/Msys is not supported by jimtcl. Is that not true? > > That is *not* true. > The version of jimtcl in openocd-0.5.0 fully supports building on mingw/msys > Seems this is true and it works without using Cygwin. Thanks for the information. /c/cygwin/home/xfchen/openocd/openocd-0.5.0/build_mingw_direct $ ../configure --enable-jlink --enable-ft2232_libftdi checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ISO C99... -std=gnu99 checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for ranlib... ranlib checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc -std=gnu99... c:/mingw/mingw32/bin/ld.exe checking if the linker (c:/mingw/mingw32/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /mingw/bin/nm checking the name lister (/mingw/bin/nm) interface... BSD nm checking whether ln -s works... no, using cp -p checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-mingw32 file names to i686-pc-mingw32 format... func_convert_file_msys_to_w32 checking how to convert i686-pc-mingw32 file names to toolchain format... func_c onvert_file_msys_to_w32 checking for c:/mingw/mingw32/bin/ld.exe option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... file_magic ^x86 archive import| ^x86 DLL checking for dlltool... dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_imp lib checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... (cached) ranlib checking command to parse /mingw/bin/nm output from gcc -std=gnu99 object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -std=gnu99 -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... no checking for objdir... .libs checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no checking for gcc -std=gnu99 option to produce PIC... -DDLL_EXPORT -DPIC checking if gcc -std=gnu99 PIC flag -DDLL_EXPORT -DPIC works... yes checking if gcc -std=gnu99 static flag -static works... yes checking if gcc -std=gnu99 supports -c -o file.o... yes checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes checking whether the gcc -std=gnu99 linker (c:/mingw/mingw32/bin/ld.exe) support s shared libraries... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking for an ANSI C-conforming const... yes checking for long long int... yes checking for library containing ioperm... no checking for library containing dlopen... no checking sys/socket.h usability... no checking sys/socket.h presence... no checking for sys/socket.h... no checking for arpa/inet.h... no checking elf.h usability... no checking elf.h presence... no checking for elf.h... no checking dirent.h usability... yes checking dirent.h presence... yes checking for dirent.h... yes checking fcntl.h usability.
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken wrote: > Hi Xiaofan > > In my case I struggled with the same problem for a day or two. That is why > I need to know if it is the checkout of the version, or the updating of the > mingw32 compiler that fixed the problem. > > After doing the ./bootstrap command, the head revision of JimTCL is cloned > from its repository - afaik. Thus, to get version 0.63 checked out do the > following > cd jimtcl > git tag -l (Gives you a list of the tags for the jimtcl repository) > git checkout 0.63 > > The version of Jimtcl in the directory should now be 0.63. To view the tags > of the openocd source, and checkout for instance 0.5.0-rc2 the same > procedure is used. > > Hopefully this helps, cause I've been trying to replicate the problem > without success for a while now. > This is clear now. I will make sure that my MinGW/Cygwin setup are up to date and see if that helps. If not, I will follow your suggestion and downgrade jimtcl to see if that help. Thanks for the helps! -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10/08/2011, at 3:03 PM, Xiaofan Chen wrote: > On Wed, Aug 10, 2011 at 11:44 AM, Steve Bennett > wrote: >> On 10/08/2011, at 9:43 AM, Xiaofan Chen wrote: >>> It was not up to date but very close. Anyway, I just updated it and >>> the issue is still there with the release zip file. I will try the git >>> tree later. >>> >>> === configuring in jimtcl >>> (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr >>> oss/jimtcl) >>> configure: running /bin/sh ../../jimtcl/configure.gnu >>> --disable-option-checking >>> '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' >>> '--enable-ft22 >>> 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null >>> --srcdir=../../ >>> jimtcl >>> ../../jimtcl/configure: line 3: >>> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >>> : No such file or directory >>> ../../jimtcl/configure: line 3: exec: >>> D:/work/openocd/openocd-0.5.0/jimtcl/autos >>> : cannot execute: No such file or directory >>> configure: error: ../../jimtcl/configure.gnu failed for jimtcl >> >> You have something weird going on there. Note how the lines are truncated. >> For example: >> >>> ../../jimtcl/configure: line 3: >>> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >>> : No such file or directory > > Yes I agree that the error message is quite strange. It is directly copy > and paste from the Cygwin prompt. I will check again. > > The other errors under MinGW are also quite strange. I think I will > try another setup. Let us know how that goes. > >> Or is that your cut and paste of the error messages? >> If so, please add the errors as an attachment instead. >> >> FYI: I build the release tarball on windows/mingw without any problems. > > Glad to know that. As per the previous answer from Spen that > MinGW/Msys is not supported by jimtcl. Is that not true? That is *not* true. The version of jimtcl in openocd-0.5.0 fully supports building on mingw/msys Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 11:44 AM, Steve Bennett wrote: > On 10/08/2011, at 9:43 AM, Xiaofan Chen wrote: >> It was not up to date but very close. Anyway, I just updated it and >> the issue is still there with the release zip file. I will try the git >> tree later. >> >> === configuring in jimtcl >> (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr >> oss/jimtcl) >> configure: running /bin/sh ../../jimtcl/configure.gnu >> --disable-option-checking >> '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' >> '--enable-ft22 >> 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null >> --srcdir=../../ >> jimtcl >> ../../jimtcl/configure: line 3: >> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >> : No such file or directory >> ../../jimtcl/configure: line 3: exec: >> D:/work/openocd/openocd-0.5.0/jimtcl/autos >> : cannot execute: No such file or directory >> configure: error: ../../jimtcl/configure.gnu failed for jimtcl > > You have something weird going on there. Note how the lines are truncated. > For example: > >> ../../jimtcl/configure: line 3: >> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >> : No such file or directory Yes I agree that the error message is quite strange. It is directly copy and paste from the Cygwin prompt. I will check again. The other errors under MinGW are also quite strange. I think I will try another setup. > Or is that your cut and paste of the error messages? > If so, please add the errors as an attachment instead. > > FYI: I build the release tarball on windows/mingw without any problems. Glad to know that. As per the previous answer from Spen that MinGW/Msys is not supported by jimtcl. Is that not true? -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 10/08/2011, at 9:43 AM, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 11:11 PM, Spencer Oliver wrote: >> On 9 August 2011 16:01, Xiaofan Chen wrote: >>> On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver >>> wrote: >>> Just tested building native windoze under cygwin and working fine here. I used the release tarball and the following configure line: ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 --disable-shared --disable-werror --enable-ft2232_ftd2xx >>> >>> Try build in a separate build directory and see if that is okay >>> or not. >>> >> >> works fine in/out of src tree. >> Just to be sure i also deleted the release src tree between builds. >> >> are your cygwin tools upto date? > > It was not up to date but very close. Anyway, I just updated it and > the issue is still there with the release zip file. I will try the git > tree later. > > === configuring in jimtcl > (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr > oss/jimtcl) > configure: running /bin/sh ../../jimtcl/configure.gnu > --disable-option-checking > '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' > '--enable-ft22 > 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null > --srcdir=../../ > jimtcl > ../../jimtcl/configure: line 3: > D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j > : No such file or directory > ../../jimtcl/configure: line 3: exec: > D:/work/openocd/openocd-0.5.0/jimtcl/autos > : cannot execute: No such file or directory > configure: error: ../../jimtcl/configure.gnu failed for jimtcl You have something weird going on there. Note how the lines are truncated. For example: > ../../jimtcl/configure: line 3: > D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j > : No such file or directory Or is that your cut and paste of the error messages? If so, please add the errors as an attachment instead. FYI: I build the release tarball on windows/mingw without any problems. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 7:59 AM, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 11:26 PM, Olivier Schonken > wrote: >> Hi Xiaofan >> >> I also experienced the same build error a while ago. To fix it I manually >> checked out version 0.63 of JimTCL, > > Just wondering how you do that? I mean to ask the following question. Do you check out 0.63 version of JimTCL and replace the JimTCL in 0.5.0 release (or latest git) with the 0.63 version of JimTCL? -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 11:26 PM, Olivier Schonken wrote: > Hi Xiaofan > > I also experienced the same build error a while ago. To fix it I manually > checked out version 0.63 of JimTCL, Just wondering how you do that? > and after that, the build went on > without any problems. I did a git clone of openocd just-now, and I did a > --host="i686-w64-mingw32" build on a Windows 7 installation of cygwin, and > it compiled without a hitch. > > Please let me know if this doesn't help. I tried the 64bit cross build and it is still the same issue. The error messages are quite strange though. cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-win32compat .o ../../jimtcl/jim-win32compat.c cc1: warnings being treated as errors ../../jimtcl/jim-win32compat.c: In function ‘dlopen’: ../../jimtcl/jim-win32compat.c:9: error: implicit declaration of function ‘Load LibraryA’ ../../jimtcl/jim-win32compat.c: In function ‘dlclose’: ../../jimtcl/jim-win32compat.c:14: error: implicit declaration of function ‘Fre eLibrary’ ../../jimtcl/jim-win32compat.c:14: error: ‘HANDLE’ undeclared (first use in th is function) ../../jimtcl/jim-win32compat.c:14: error: (Each undeclared identifier is reporte d only once ../../jimtcl/jim-win32compat.c:14: error: for each function it appears in.) ../../jimtcl/jim-win32compat.c:14: error: expected ‘)’ before ‘handle’ ../../jimtcl/jim-win32compat.c: In function ‘dlsym’: ../../jimtcl/jim-win32compat.c:20: error: implicit declaration of function ‘Get ProcAddress’ ../../jimtcl/jim-win32compat.c:20: error: ‘HMODULE’ undeclared (first use in t his function) ../../jimtcl/jim-win32compat.c:20: error: expected ‘)’ before ‘handle’ ../../jimtcl/jim-win32compat.c:20: error: return makes pointer from integer with out a cast ../../jimtcl/jim-win32compat.c: In function ‘dlerror’: ../../jimtcl/jim-win32compat.c:26: error: implicit declaration of function ‘For matMessageA’ ../../jimtcl/jim-win32compat.c:26: error: ‘FORMAT_MESSAGE_FROM_SYSTEM’ undecla red (first use in this function) ../../jimtcl/jim-win32compat.c:26: error: implicit declaration of function ‘Get LastError’ ../../jimtcl/jim-win32compat.c:27: error: ‘LANG_NEUTRAL’ undeclared (first use in this function) make[2]: *** [jim-win32compat.o] Error 1 make[2]: Leaving directory `/cygdrive/d/work/openocd/openocd/build-crossmingw64/ jimtcl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/cygdrive/d/work/openocd/openocd/build-crossmingw64' make: *** [all] Error 2 -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 11:11 PM, Spencer Oliver wrote: > On 9 August 2011 16:01, Xiaofan Chen wrote: >> On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: >> >>> Just tested building native windoze under cygwin and working fine here. >>> I used the release tarball and the following configure line: >>> ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 >>> --disable-shared --disable-werror --enable-ft2232_ftd2xx >> >> Try build in a separate build directory and see if that is okay >> or not. >> > > works fine in/out of src tree. > Just to be sure i also deleted the release src tree between builds. > > are your cygwin tools upto date? It was not up to date but very close. Anyway, I just updated it and the issue is still there with the release zip file. I will try the git tree later. === configuring in jimtcl (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr oss/jimtcl) configure: running /bin/sh ../../jimtcl/configure.gnu --disable-option-checking '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' '--enable-ft22 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null --srcdir=../../ jimtcl ../../jimtcl/configure: line 3: D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j : No such file or directory ../../jimtcl/configure: line 3: exec: D:/work/openocd/openocd-0.5.0/jimtcl/autos : cannot execute: No such file or directory configure: error: ../../jimtcl/configure.gnu failed for jimtcl -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
Hi Xiaofan I also experienced the same build error a while ago. To fix it I manually checked out version 0.63 of JimTCL, and after that, the build went on without any problems. I did a git clone of openocd just-now, and I did a --host="i686-w64-mingw32" build on a Windows 7 installation of cygwin, and it compiled without a hitch. Please let me know if this doesn't help. Regards Olivier Subject: Re: [Openocd-development] 0.5.0 MinGW configure failure Message-ID: Content-Type: text/plain; charset=windows-1252 On Tue, Aug 9, 2011 at 10:05 PM, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 9:47 PM, Xiaofan Chen wrote: >> On Tue, Aug 9, 2011 at 9:27 PM, Spencer Oliver wrote: >>> The issue is building using msys under windoze. >>> Using cygwin or linux to build native win32 (mingw) is not an issue. >>> >> >> I remember there were no issues to build MinGW binary under >> Cygwin with the cross compiler with OpenOCD git. But it seems >> that there are problems with the 0.5.0 release tar ball. >> >> Actually build under Cygwin is also problematic. > > Luckily git tree is still okay for Cygwin native build and > Cygwin MinGW cross build. > But only Cygwin native build is okay. $ openocd -v Open On-Chip Debugger 0.6.0-dev-2-gdb87a2f-dirty (2011-08-09-22:03) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html MinGW cross build under Cygwin fails because of jimtcl. mcuee@mcuee-PC-Win7 /cygdrive/d/work/openocd/openocd/build-crossmingw $ make make all-recursive make[1]: Entering directory `/cygdrive/d/work/openocd/openocd/build-crossmingw' Making all in jimtcl make[2]: Entering directory `/cygdrive/d/work/openocd/openocd/build-crossmingw/j imtcl' /cygdrive/d/work/openocd/openocd/build-crossmingw/jimtcl/../../jimtcl/autosetup/ jimsh0 ../../jimtcl/make-load-static-exts.tcl aio array clock eventloop exec fil e load nvp package posix readdir regexp signal syslog glob stdlib tclcompat >_lo ad-static-exts.c || ( rm _load-static-exts.c; exit 1) cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o _load-static-ex ts.o _load-static-exts.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-subcmd.o .. /../jimtcl/jim-subcmd.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-interactive .o ../../jimtcl/jim-interactive.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-format.o .. /../jimtcl/jim-format.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim.o ../../jim tcl/jim.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o utf8.o ../../ji mtcl/utf8.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jimregexp.o ../ ../jimtcl/jimregexp.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-win32compat .o ../../jimtcl/jim-win32compat.c cc1: warnings being treated as errors ../../jimtcl/jim-win32compat.c: In function ?dlopen?: ../../jimtcl/jim-win32compat.c:9: error: implicit declaration of function ?LoadLibraryA? ../../jimtcl/jim-win32compat.c: In function ?dlclose?: ../../jimtcl/jim-win32compat.c:14: error: implicit declaration of function ?FreeLibrary? ../../jimtcl/jim-win32compat.c:14: error: ?HANDLE? undeclared (first use in this function) ../../jimtcl/jim-win32compat.c:14: error: (Each undeclared identifier is reported only once ../../jimtcl/jim-win32compat.c:14: error: for each function it appears in.) ../../jimtcl/jim-win32compat.c:14: error: expected ?)? before ?handle? ../../jimtcl/jim-win32compat.c: In function ?dlsym?: ../../jimtcl/jim-win32compat.c:20: error: implicit declaration of function ?GetProcAddress? ../../jimtcl/jim-win32compat.c:20: error: ?HMODULE? undeclared (first use in this function) ../../jimtcl/jim-win32compat.c:20: error: expected ?)? before ?handle? ../../jimtcl/jim-win32compat.c:20: error: return makes pointer from integer without a cast ../../jimtcl/jim-win32compat.c: In function ?dlerror?: ../../jimtcl/jim-win32compat.c:26: error: implicit declaration of function ?FormatMessageA? ../../jimtcl/jim-win32compat.c:26: error: ?FORMAT_MESSAGE_FROM_SYSTEM? undeclared (first use in this function) ../../jimtcl/jim-win32compat.c:26: error: implicit declaration of function ?GetLastError? ../../jimtcl/jim-win32compat.c:27: error: ?LANG_NEUTRAL? undeclared (first use in this function) make[2]: *** [jim-win32compat.o] Error 1 make[2]: Leaving directory `/cygdrive/d/work/openocd/openocd/build-crossmingw/jimtcl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/cygdrive/d/work/openocd/openocd/build-crossmingw' make: *** [all] Error 2 <2mcuee@mcuee-PC-Win7> mcuee@mcuee-PC-Win7 <2mcuee@mcuee-PC-Win7> /cygdrive/d/work/openocd/openocd/build-crossmingw $ i686-pc-mingw32-gcc -v Using built-in specs. COLLECT_GCC=i686-pc-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/li
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 9 August 2011 16:11, Spencer Oliver wrote: > On 9 August 2011 16:01, Xiaofan Chen wrote: >> On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: >> >>> Just tested building native windoze under cygwin and working fine here. >>> I used the release tarball and the following configure line: >>> ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 >>> --disable-shared --disable-werror --enable-ft2232_ftd2xx >> >> Try build in a separate build directory and see if that is okay >> or not. >> > > works fine in/out of src tree. > Just to be sure i also deleted the release src tree between builds. > > are your cygwin tools upto date? > can you run make distcheck on your normal dev tree. This is what has been used to check that the release tarball works. Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 9 August 2011 16:01, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: > >> Just tested building native windoze under cygwin and working fine here. >> I used the release tarball and the following configure line: >> ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 >> --disable-shared --disable-werror --enable-ft2232_ftd2xx > > Try build in a separate build directory and see if that is okay > or not. > works fine in/out of src tree. Just to be sure i also deleted the release src tree between builds. are your cygwin tools upto date? Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 10:20 PM, Spencer Oliver wrote: > Just tested building native windoze under cygwin and working fine here. > I used the release tarball and the following configure line: > ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 > --disable-shared --disable-werror --enable-ft2232_ftd2xx Try build in a separate build directory and see if that is okay or not. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 9 August 2011 15:10, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 10:05 PM, Xiaofan Chen wrote: >> On Tue, Aug 9, 2011 at 9:47 PM, Xiaofan Chen wrote: >>> On Tue, Aug 9, 2011 at 9:27 PM, Spencer Oliver wrote: The issue is building using msys under windoze. Using cygwin or linux to build native win32 (mingw) is not an issue. >>> >>> I remember there were no issues to build MinGW binary under >>> Cygwin with the cross compiler with OpenOCD git. But it seems >>> that there are problems with the 0.5.0 release tar ball. >>> >>> Actually build under Cygwin is also problematic. >> >> Luckily git tree is still okay for Cygwin native build and >> Cygwin MinGW cross build. >> > > But only Cygwin native build is okay. > $ openocd -v > Open On-Chip Debugger 0.6.0-dev-2-gdb87a2f-dirty (2011-08-09-22:03) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > > > MinGW cross build under Cygwin fails because of jimtcl. > > Just tested building native windoze under cygwin and working fine here. I used the release tarball and the following configure line: ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32 --disable-shared --disable-werror --enable-ft2232_ftd2xx Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 10:05 PM, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 9:47 PM, Xiaofan Chen wrote: >> On Tue, Aug 9, 2011 at 9:27 PM, Spencer Oliver wrote: >>> The issue is building using msys under windoze. >>> Using cygwin or linux to build native win32 (mingw) is not an issue. >>> >> >> I remember there were no issues to build MinGW binary under >> Cygwin with the cross compiler with OpenOCD git. But it seems >> that there are problems with the 0.5.0 release tar ball. >> >> Actually build under Cygwin is also problematic. > > Luckily git tree is still okay for Cygwin native build and > Cygwin MinGW cross build. > But only Cygwin native build is okay. $ openocd -v Open On-Chip Debugger 0.6.0-dev-2-gdb87a2f-dirty (2011-08-09-22:03) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html MinGW cross build under Cygwin fails because of jimtcl. mcuee@mcuee-PC-Win7 /cygdrive/d/work/openocd/openocd/build-crossmingw $ make make all-recursive make[1]: Entering directory `/cygdrive/d/work/openocd/openocd/build-crossmingw' Making all in jimtcl make[2]: Entering directory `/cygdrive/d/work/openocd/openocd/build-crossmingw/j imtcl' /cygdrive/d/work/openocd/openocd/build-crossmingw/jimtcl/../../jimtcl/autosetup/ jimsh0 ../../jimtcl/make-load-static-exts.tcl aio array clock eventloop exec fil e load nvp package posix readdir regexp signal syslog glob stdlib tclcompat >_lo ad-static-exts.c || ( rm _load-static-exts.c; exit 1) cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o _load-static-ex ts.o _load-static-exts.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-subcmd.o .. /../jimtcl/jim-subcmd.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-interactive .o ../../jimtcl/jim-interactive.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-format.o .. /../jimtcl/jim-format.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim.o ../../jim tcl/jim.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o utf8.o ../../ji mtcl/utf8.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jimregexp.o ../ ../jimtcl/jimregexp.c cc -g -O2 -D_GNU_SOURCE -Wall -Werror -I. -I../../jimtcl -c -o jim-win32compat .o ../../jimtcl/jim-win32compat.c cc1: warnings being treated as errors ../../jimtcl/jim-win32compat.c: In function ‘dlopen’: ../../jimtcl/jim-win32compat.c:9: error: implicit declaration of function ‘LoadLibraryA’ ../../jimtcl/jim-win32compat.c: In function ‘dlclose’: ../../jimtcl/jim-win32compat.c:14: error: implicit declaration of function ‘FreeLibrary’ ../../jimtcl/jim-win32compat.c:14: error: ‘HANDLE’ undeclared (first use in this function) ../../jimtcl/jim-win32compat.c:14: error: (Each undeclared identifier is reported only once ../../jimtcl/jim-win32compat.c:14: error: for each function it appears in.) ../../jimtcl/jim-win32compat.c:14: error: expected ‘)’ before ‘handle’ ../../jimtcl/jim-win32compat.c: In function ‘dlsym’: ../../jimtcl/jim-win32compat.c:20: error: implicit declaration of function ‘GetProcAddress’ ../../jimtcl/jim-win32compat.c:20: error: ‘HMODULE’ undeclared (first use in this function) ../../jimtcl/jim-win32compat.c:20: error: expected ‘)’ before ‘handle’ ../../jimtcl/jim-win32compat.c:20: error: return makes pointer from integer without a cast ../../jimtcl/jim-win32compat.c: In function ‘dlerror’: ../../jimtcl/jim-win32compat.c:26: error: implicit declaration of function ‘FormatMessageA’ ../../jimtcl/jim-win32compat.c:26: error: ‘FORMAT_MESSAGE_FROM_SYSTEM’ undeclared (first use in this function) ../../jimtcl/jim-win32compat.c:26: error: implicit declaration of function ‘GetLastError’ ../../jimtcl/jim-win32compat.c:27: error: ‘LANG_NEUTRAL’ undeclared (first use in this function) make[2]: *** [jim-win32compat.o] Error 1 make[2]: Leaving directory `/cygdrive/d/work/openocd/openocd/build-crossmingw/jimtcl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/cygdrive/d/work/openocd/openocd/build-crossmingw' make: *** [all] Error 2 mcuee@mcuee-PC-Win7 /cygdrive/d/work/openocd/openocd/build-crossmingw $ i686-pc-mingw32-gcc -v Using built-in specs. COLLECT_GCC=i686-pc-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-mingw32/4.5.2/lto-wrapper.exe Target: i686-pc-mingw32 Configured with: /usr/src/packages/mingw-gcc/mingw-gcc-4.5.2-1/src/gcc-4.5.2/con figure --srcdir=/usr/src/packages/mingw-gcc/mingw-gcc-4.5.2-1/src/gcc-4.5.2 --pr efix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir= /usr/lib --datadir=/usr/share --localstatedir=/var --sysconfdir=/etc --datarootd ir=/usr/share --docdir=/usr/share/doc/mingw-gcc -C --build=i686-pc-cygwin --host =i686-pc-cygwin --target=i686-pc-mingw32 --with-sysroot=/usr/i686-pc-mingw32/sys -root --with-build-sysroot=/usr/i686-pc-mingw32/sys-root --disable-multilib --di sable-win32-registry --enable-languages=c,c++,fortran,objc,obj-c++ --enable-libg om
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 9:47 PM, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 9:27 PM, Spencer Oliver wrote: >> The issue is building using msys under windoze. >> Using cygwin or linux to build native win32 (mingw) is not an issue. >> > > I remember there were no issues to build MinGW binary under > Cygwin with the cross compiler with OpenOCD git. But it seems > that there are problems with the 0.5.0 release tar ball. > > Actually build under Cygwin is also problematic. Luckily git tree is still okay for Cygwin native build and Cygwin MinGW cross build. mcuee@mcuee-PC-Win7 /cygdrive/d/work/openocd/openocd/build-crossmingw $ ../configure --enable-maintainer-mode --build=i686-pc-mingw32 --enable-jlink --enable-ft2232_libftdi checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ISO C99... -std=gnu99 checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for ranlib... ranlib checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc -std=gnu99... /usr/i686-pc-cygwin/bin/ld.exe checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-mingw32 file names to i686-pc-mingw32 format... func_convert_file_msys_to_w32 checking how to convert i686-pc-mingw32 file names to toolchain format... func_c onvert_file_msys_to_w32 checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... file_magic ^x86 archive import| ^x86 DLL checking for dlltool... dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_imp lib checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... (cached) ranlib checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -std=gnu99 -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no checking for gcc -std=gnu99 option to produce PIC... -DDLL_EXPORT -DPIC checking if gcc -std=gnu99 PIC flag -DDLL_EXPORT -DPIC works... yes checking if gcc -std=gnu99 static flag -static works... no checking if gcc -std=gnu99 supports -c -o file.o... yes checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes checking whether the gcc -std=gnu99 linker (/usr/i686-pc-cygwin/bin/ld.exe) supp orts shared libraries... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking for an ANSI C-conforming const... yes checking for long long int... yes checking for library containing ioperm... -lioperm checking for library containing dlopen... none required checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking for arpa/inet.h... yes checking elf.h usability... yes checki
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 9:27 PM, Spencer Oliver wrote: > The issue is building using msys under windoze. > Using cygwin or linux to build native win32 (mingw) is not an issue. > I remember there were no issues to build MinGW binary under Cygwin with the cross compiler with OpenOCD git. But it seems that there are problems with the 0.5.0 release tar ball. Actually build under Cygwin is also problematic. mcuee@mcuee-PC-Win7 /cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cross $ ../configure --build=i686-pc-mingw32 --enable-jlink --enable-ft2232_libftdi checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ISO C99... -std=gnu99 checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for ranlib... ranlib checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc -std=gnu99... /usr/i686-pc-cygwin/bin/ld.exe checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-mingw32 file names to i686-pc-mingw32 format... func_convert_file_msys_to_w32 checking how to convert i686-pc-mingw32 file names to toolchain format... func_c onvert_file_msys_to_w32 checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... file_magic ^x86 archive import| ^x86 DLL checking for dlltool... dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_imp lib checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... (cached) ranlib checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -std=gnu99 -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no checking for gcc -std=gnu99 option to produce PIC... -DDLL_EXPORT -DPIC checking if gcc -std=gnu99 PIC flag -DDLL_EXPORT -DPIC works... yes checking if gcc -std=gnu99 static flag -static works... no checking if gcc -std=gnu99 supports -c -o file.o... yes checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes checking whether the gcc -std=gnu99 linker (/usr/i686-pc-cygwin/bin/ld.exe) supp orts shared libraries... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking for an ANSI C-conforming const... yes checking for long long int... yes checking for library containing ioperm... -lioperm checking for library containing dlopen... none required checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking for arpa/inet.h... yes checking elf.h usability... yes checking elf.h presence... yes checking for elf.h... yes checking dirent.h usability... yes checking dirent.h presence... yes checking for dirent.h... yes checking fcntl.h usabili
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 9 August 2011 14:34, Xiaofan Chen wrote: > On Tue, Aug 9, 2011 at 9:25 PM, Spencer Oliver wrote: >> On 9 August 2011 13:48, Vit Mares wrote: >>> it doesn't seem so, jimsh0.exe is built during configure and is runable. >>> When I start it in MSYS console I get the dot prompt. >>> >> It has been a while since i looked however: >> Building jimsh0 is not the problem, running it is - the scripts look >> for jimsh0 and under msys this should be jimsh0.exe. >> > > Just wondering if this could be fixed. I think many Windows > users would like to be able to build under MinGW/MSys > instead of Cygwin (quite slow). > Hoping it will get fixed, however that part is todo with jimtcl and i do not understand their build system. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 9:25 PM, Spencer Oliver wrote: > On 9 August 2011 13:48, Vit Mares wrote: >> it doesn't seem so, jimsh0.exe is built during configure and is runable. >> When I start it in MSYS console I get the dot prompt. >> > It has been a while since i looked however: > Building jimsh0 is not the problem, running it is - the scripts look > for jimsh0 and under msys this should be jimsh0.exe. > Just wondering if this could be fixed. I think many Windows users would like to be able to build under MinGW/MSys instead of Cygwin (quite slow). -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 9 August 2011 14:13, Jie Zhang wrote: > On Tue, Aug 9, 2011 at 7:52 AM, Vit Mares wrote: >> Attempt to build 0.5.0 with MinGW on Windows XP failed when running >> configure. >> Release 0.4.0 configured and built without problems. > > I downloaded 0.5.0 and built it with mingw-w64 on Debian testing. The > build was successful. But I didn't try the resulted binary. > The issue is building using msys under windoze. Using cygwin or linux to build native win32 (mingw) is not an issue. Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 9 August 2011 13:48, Vit Mares wrote: > Hi Spen, > > it doesn't seem so, jimsh0.exe is built during configure and is runable. > When I start it in MSYS console I get the dot prompt. > > Best regards > Vit > It has been a while since i looked however: Building jimsh0 is not the problem, running it is - the scripts look for jimsh0 and under msys this should be jimsh0.exe. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Tue, Aug 9, 2011 at 7:52 AM, Vit Mares wrote: > Attempt to build 0.5.0 with MinGW on Windows XP failed when running configure. > Release 0.4.0 configured and built without problems. I downloaded 0.5.0 and built it with mingw-w64 on Debian testing. The build was successful. But I didn't try the resulted binary. Jie ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
Hi Spen, it doesn't seem so, jimsh0.exe is built during configure and is runable. When I start it in MSYS console I get the dot prompt. Best regards Vit 2011/8/9 Spencer Oliver : > On 9 August 2011 12:52, Vit Mares wrote: >> Attempt to build 0.5.0 with MinGW on Windows XP failed when running >> configure. >> Release 0.4.0 configured and built without problems. >> >> config.status: creating src/pld/Makefile >> config.status: creating doc/Makefile >> config.status: creating config.h >> config.status: config.h is unchanged >> config.status: executing depfiles commands >> config.status: executing libtool commands >> === configuring in jimtcl (/home/maresv/openocd-0.5.0/jimtcl) >> configure: running /bin/sh ./configure.gnu --disable-option-checking >> '--prefix=/home/maresv/openocd_dist_050' '--enable >> -parport' '--enable-parport-giveio' '--enable-ft2232_ftd2xx' >> '--with-ftd2xx-win32-zipdir=/home/maresv/drivers_ftdi' --ca >> che-file=/dev/null --srcdir=. >> The system cannot find the path specified. >> autosetup/system.tcl:150: Error: >> in procedure 'use' called at file "auto.def", line 5 >> in procedure 'use' called at file "autosetup/cc.tcl", line 29 >> in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 >> Try: 'configure --debug' for a full stack trace >> configure: error: ./configure.gnu failed for jimtcl >> >> Best regards >> Vit Mares >> > > As far as i am aware jimtcl does not support building under msys. > I have tested building win32/64 native binaries under cygwin and linux > - both these are working. > > Cheers > Spen > ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On 9 August 2011 12:52, Vit Mares wrote: > Attempt to build 0.5.0 with MinGW on Windows XP failed when running configure. > Release 0.4.0 configured and built without problems. > > config.status: creating src/pld/Makefile > config.status: creating doc/Makefile > config.status: creating config.h > config.status: config.h is unchanged > config.status: executing depfiles commands > config.status: executing libtool commands > === configuring in jimtcl (/home/maresv/openocd-0.5.0/jimtcl) > configure: running /bin/sh ./configure.gnu --disable-option-checking > '--prefix=/home/maresv/openocd_dist_050' '--enable > -parport' '--enable-parport-giveio' '--enable-ft2232_ftd2xx' > '--with-ftd2xx-win32-zipdir=/home/maresv/drivers_ftdi' --ca > che-file=/dev/null --srcdir=. > The system cannot find the path specified. > autosetup/system.tcl:150: Error: > in procedure 'use' called at file "auto.def", line 5 > in procedure 'use' called at file "autosetup/cc.tcl", line 29 > in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 > Try: 'configure --debug' for a full stack trace > configure: error: ./configure.gnu failed for jimtcl > > Best regards > Vit Mares > As far as i am aware jimtcl does not support building under msys. I have tested building win32/64 native binaries under cygwin and linux - both these are working. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] 0.5.0 MinGW configure failure
Attempt to build 0.5.0 with MinGW on Windows XP failed when running configure. Release 0.4.0 configured and built without problems. config.status: creating src/pld/Makefile config.status: creating doc/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands === configuring in jimtcl (/home/maresv/openocd-0.5.0/jimtcl) configure: running /bin/sh ./configure.gnu --disable-option-checking '--prefix=/home/maresv/openocd_dist_050' '--enable -parport' '--enable-parport-giveio' '--enable-ft2232_ftd2xx' '--with-ftd2xx-win32-zipdir=/home/maresv/drivers_ftdi' --ca che-file=/dev/null --srcdir=. The system cannot find the path specified. autosetup/system.tcl:150: Error: in procedure 'use' called at file "auto.def", line 5 in procedure 'use' called at file "autosetup/cc.tcl", line 29 in procedure 'config_guess' called at file "autosetup/system.tcl", line 150 Try: 'configure --debug' for a full stack trace configure: error: ./configure.gnu failed for jimtcl Best regards Vit Mares ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
