Re: [OpenOCD-devel] xPack build for OpenOCD is broken
Hi @Liviu > "Sure, I concentrated deeply all night long and fixed it with the power of my > mind. :-)" Thanks! Your witchcraft is highly appreciated. Humble greetings, Kristof - Oorspronkelijk bericht - Van: "Liviu Ionescu" Aan: "kristof mulier" Cc: "openocd-devel" Verzonden: Zaterdag 21 maart 2020 11:04:55 Onderwerp: Re: xPack build for OpenOCD is broken > On 21 Mar 2020, at 12:00, kristof.mul...@telenet.be wrote: > > The build is no longer broken. Sure, I concentrated deeply all night long and fixed it with the power of my mind. :-) > Thanks for your replies > yesterday :-) You're welcome! Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] xPack build for OpenOCD is broken
> On 21 Mar 2020, at 12:00, kristof.mul...@telenet.be wrote: > > The build is no longer broken. Sure, I concentrated deeply all night long and fixed it with the power of my mind. :-) > Thanks for your replies > yesterday :-) You're welcome! Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] xPack build for OpenOCD is broken
Hi Liviu, I just compiled OpenOCD successfully using xPacks. The build is no longer broken. Thanks for your replies yesterday :-) - Oorspronkelijk bericht - Van: "Liviu Ionescu" Aan: "kristof mulier" Cc: "openocd-devel" Verzonden: Vrijdag 20 maart 2020 17:22:34 Onderwerp: Re: xPack build for OpenOCD is broken > On 20 Mar 2020, at 18:07, kristof.mul...@telenet.be wrote: > > Hi Liviu, > > Many thanks for your quick reply. I'm happy to hear you're working on > the xPack Build Box (v3.1). Your efforts to make software like OpenOCD > easier to build, makes it available to much more people. > You're my hero! Thank you! Once the new build environment will be in place it'll be also easier for myself to make new releases. Perhaps we can agree on a schedule, and make the xPack binaries the default/recommended OpenOCD binaries, for those who do not want to bother with compiling them from sources. As such, you would not have to run the scripts yourself. > You said: >> "Most probably the urls need to be moved away from SourceForge" > > I agree. SourceForge is flooded with ads. They're flickering all > over the place. I believe a software like OpenOCD deserves a better > place to live. The adds are only annoying, I don't mind them since I visit the site very rarely, but the timeouts are benign. Now it seems https://repo.or.cz suffers from similar issues. Personally I would move the project to GitHub. Create an organisation called OpenOCD and transfer everything there. Regards, Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] xPack build for OpenOCD is broken
Hi @Liviu, You said: > "Perhaps we can agree on a schedule, and make the xPack binaries the > default/recommended OpenOCD binaries, for those who do not want to > bother with compiling them from sources." I agree full 100%. Perhaps they can be even made downloadable from the official OpenOCD website? You also said: > "As such, you would not have to run the scripts yourself." That would be true for 95% of the users. But sometimes I need the bleeding-edge-version to try some fix that someone pushed for some specific microcontroller. I'm trying out all sorts of microcontroller boards, adding them to our new free microcontroller IDE (see https://embeetle.com) Shouldn't OpenOCD have a logo? I've designed one that can be used: https://embeetle.com/icons/tools/openocd.png and for the combo OpenOCD + GDB: https://embeetle.com/icons/tools/openocd_gdb.png Any ideas? Kind greetings, Kristof Mulier - Oorspronkelijk bericht - Van: "Liviu Ionescu" Aan: "kristof mulier" Cc: "openocd-devel" Verzonden: Vrijdag 20 maart 2020 17:22:34 Onderwerp: Re: xPack build for OpenOCD is broken > On 20 Mar 2020, at 18:07, kristof.mul...@telenet.be wrote: > > Hi Liviu, > > Many thanks for your quick reply. I'm happy to hear you're working on > the xPack Build Box (v3.1). Your efforts to make software like OpenOCD > easier to build, makes it available to much more people. > You're my hero! Thank you! Once the new build environment will be in place it'll be also easier for myself to make new releases. Perhaps we can agree on a schedule, and make the xPack binaries the default/recommended OpenOCD binaries, for those who do not want to bother with compiling them from sources. As such, you would not have to run the scripts yourself. > You said: >> "Most probably the urls need to be moved away from SourceForge" > > I agree. SourceForge is flooded with ads. They're flickering all > over the place. I believe a software like OpenOCD deserves a better > place to live. The adds are only annoying, I don't mind them since I visit the site very rarely, but the timeouts are benign. Now it seems https://repo.or.cz suffers from similar issues. Personally I would move the project to GitHub. Create an organisation called OpenOCD and transfer everything there. Regards, Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] xPack build for OpenOCD is broken
> On 20 Mar 2020, at 18:07, kristof.mul...@telenet.be wrote: > > Hi Liviu, > > Many thanks for your quick reply. I'm happy to hear you're working on > the xPack Build Box (v3.1). Your efforts to make software like OpenOCD > easier to build, makes it available to much more people. > You're my hero! Thank you! Once the new build environment will be in place it'll be also easier for myself to make new releases. Perhaps we can agree on a schedule, and make the xPack binaries the default/recommended OpenOCD binaries, for those who do not want to bother with compiling them from sources. As such, you would not have to run the scripts yourself. > You said: >> "Most probably the urls need to be moved away from SourceForge" > > I agree. SourceForge is flooded with ads. They're flickering all > over the place. I believe a software like OpenOCD deserves a better > place to live. The adds are only annoying, I don't mind them since I visit the site very rarely, but the timeouts are benign. Now it seems https://repo.or.cz suffers from similar issues. Personally I would move the project to GitHub. Create an organisation called OpenOCD and transfer everything there. Regards, Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] xPack build for OpenOCD is broken
> On 20 Mar 2020, at 17:21, kristof.mul...@telenet.be wrote: > > I'm using the xPack from @Liviu Ionescu to build OpenOCD for both Windows > and Linux. You can find more info on his website: > https://xpack.github.io/openocd/ Hi Kristof, Thank you for reporting this issue, and for using my build scripts. > https://embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build One small comment: your explanations on how to install docker are ok, but I would still use the official Docker steps: https://docs.docker.com/install/linux/docker-ce/ubuntu/ > The error message I get is printed below. I think it's an issue with the > OpenOCD git server: > > Cloning "openocd.git" from "git://git.code.sf.net/p/openocd/code"... > Cloning into 'openocd.git'... > remote: Enumerating objects: 63643, done. > remote: Counting objects: 100% (63643/63643), done. > remote: Compressing objects: 100% (27437/27437), done. > remote: Total 63643 (delta 52300), reused 43882 (delta 36038) > Receiving objects: 100% (63643/63643), 14.39 MiB | 5.97 MiB/s, done. > Resolving deltas: 100% (52300/52300), done. > Submodule 'jimtcl' (https://repo.or.cz/jimtcl.git) registered for path > 'jimtcl' > Submodule 'src/jtag/drivers/libjaylink' > (https://repo.or.cz/libjaylink.git) registered for path > 'src/jtag/drivers/libjaylink' > Submodule 'tools/git2cl' (https://repo.or.cz/git2cl.git) registered for > path 'tools/git2cl' > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl'... > fatal: unable to access 'https://repo.or.cz/jimtcl.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/jimtcl.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' failed > Failed to clone 'jimtcl'. Retry scheduled > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/src/jtag/drivers/libjaylink'... > fatal: unable to access 'https://repo.or.cz/libjaylink.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/libjaylink.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/src/jtag/drivers/libjaylink' > failed > Failed to clone 'src/jtag/drivers/libjaylink'. Retry scheduled > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/tools/git2cl'... > fatal: unable to access 'https://repo.or.cz/git2cl.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/git2cl.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/tools/git2cl' failed > Failed to clone 'tools/git2cl'. Retry scheduled > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl'... > fatal: unable to access 'https://repo.or.cz/jimtcl.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/jimtcl.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' failed > Failed to clone 'jimtcl' a second time, aborting I have no idea why this happened, but the error message is obvious, git was not able to install the submodules. > I've tried to build OpenOCD twice today, and got the same error each time. > Is this a temporary hiccup, or some URL that is pointing to something that > moved? I guess you'll get exactly the same error if you do a 'git clone --recurse-submodule git://git.code.sf.net/p/openocd/code' in any environment. I did and I got exactly the same timeouts. Most probably the urls need to be moved away from SourceForge (which is highly unreliable) and repo.or.cz. --- Since the git servers time outs are not under the control of my build scripts, I'm afraid I can't fix this. --- FYI, I'm working on a new version of the xPack Build Box (v3.1) which adds support for Arm 32/64-bits. A new version of the xPack OpenOCD binaries is scheduled soon. If you (or someone else) has any suggestions on the options I use to configure OpenOCD, I'll be grateful to hear them. https://github.com/xpack-dev-tools/openocd-xpack/blob/f2774a921d30ea63a33420f8936fc0b1851ab4fd/scripts/common-apps-functions-source.sh#L143 Best Regards, Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] xPack build for OpenOCD is broken
Hi Liviu, Many thanks for your quick reply. I'm happy to hear you're working on the xPack Build Box (v3.1). Your efforts to make software like OpenOCD easier to build, makes it available to much more people. You're my hero! You said: > "Most probably the urls need to be moved away from SourceForge" I agree. SourceForge is flooded with ads. They're flickering all over the place. I believe a software like OpenOCD deserves a better place to live. Kind greetings, Kristof - Oorspronkelijk bericht - Van: "Liviu Ionescu" Aan: "kristof mulier" Cc: "openocd-devel" Verzonden: Vrijdag 20 maart 2020 16:48:06 Onderwerp: Re: xPack build for OpenOCD is broken > On 20 Mar 2020, at 17:21, kristof.mul...@telenet.be wrote: > > I'm using the xPack from @Liviu Ionescu to build OpenOCD for both Windows > and Linux. You can find more info on his website: > https://xpack.github.io/openocd/ Hi Kristof, Thank you for reporting this issue, and for using my build scripts. > https://embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build One small comment: your explanations on how to install docker are ok, but I would still use the official Docker steps: https://docs.docker.com/install/linux/docker-ce/ubuntu/ > The error message I get is printed below. I think it's an issue with the > OpenOCD git server: > > Cloning "openocd.git" from "git://git.code.sf.net/p/openocd/code"... > Cloning into 'openocd.git'... > remote: Enumerating objects: 63643, done. > remote: Counting objects: 100% (63643/63643), done. > remote: Compressing objects: 100% (27437/27437), done. > remote: Total 63643 (delta 52300), reused 43882 (delta 36038) > Receiving objects: 100% (63643/63643), 14.39 MiB | 5.97 MiB/s, done. > Resolving deltas: 100% (52300/52300), done. > Submodule 'jimtcl' (https://repo.or.cz/jimtcl.git) registered for path > 'jimtcl' > Submodule 'src/jtag/drivers/libjaylink' > (https://repo.or.cz/libjaylink.git) registered for path > 'src/jtag/drivers/libjaylink' > Submodule 'tools/git2cl' (https://repo.or.cz/git2cl.git) registered for > path 'tools/git2cl' > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl'... > fatal: unable to access 'https://repo.or.cz/jimtcl.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/jimtcl.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' failed > Failed to clone 'jimtcl'. Retry scheduled > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/src/jtag/drivers/libjaylink'... > fatal: unable to access 'https://repo.or.cz/libjaylink.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/libjaylink.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/src/jtag/drivers/libjaylink' > failed > Failed to clone 'src/jtag/drivers/libjaylink'. Retry scheduled > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/tools/git2cl'... > fatal: unable to access 'https://repo.or.cz/git2cl.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/git2cl.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/tools/git2cl' failed > Failed to clone 'tools/git2cl'. Retry scheduled > Cloning into > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl'... > fatal: unable to access 'https://repo.or.cz/jimtcl.git/': Failed to > connect to repo.or.cz port 443: Connection timed out > fatal: clone of 'https://repo.or.cz/jimtcl.git' into submodule path > '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' failed > Failed to clone 'jimtcl' a second time, aborting I have no idea why this happened, but the error message is obvious, git was not able to install the submodules. > I've tried to build OpenOCD twice today, and got the same error each time. > Is this a temporary hiccup, or some URL that is pointing to something that > moved? I guess you'll get exactly the same error if you do a 'git clone --recurse-submodule git://git.code.sf.net/p/openocd/code' in any environment. I did and I got exactly the same timeouts. Most probably the urls need to be moved away from SourceForge (which is highly unreliable) and repo.or.cz. --- Since the git servers time outs are not under the control of my build scripts, I'm afraid I can't fix this. --- FYI, I'm working on a new version of the xPack Build Box (v3.1) which adds support for Arm 32/64-bits. A new version of the xPack OpenOCD binaries is scheduled soon. If you (or someone else) has any suggestions on the options I use to configure OpenOCD, I'll be grateful to hear them. https://github.com/xpack-dev-tools/openocd-xpack/blob/f2774a921d30ea63a33420f8936fc0b1851ab4fd/scripts/common-apps-functions-s
[OpenOCD-devel] xPack build for OpenOCD is broken
1. Background info -- Before jumping into the details, I'll first provide some background info. I'm using the xPack from @Liviu Ionescu to build OpenOCD for both Windows and Linux. You can find more info on his website: [ https://xpack.github.io/openocd/ | https://xpack.github.io/openocd/ ] I follow the instructions with a slight modification. After cloning the openocd-xpack.git, I open the file "scripts/defs-source.sh" and uncomment the last three lines. This action ensures that the latest OpenOCD source code on the master-branch gets built. 2. Sidenote --- For a step-by-step guide on how to build OpenOCD, please consult my web- page: [ https://embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build | https://embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build ] I've noted down every step of the build process - including the way I install the Ubuntu VM. It's very verbose, leaving no room for misinter- pretations :-) 3. The error message The error message I get is printed below. I think it's an issue with the OpenOCD git server: Cloning "openocd.git" from "git://git.code.sf.net/p/openocd/code" ... Cloning into 'openocd.git' ... remote: Enumerating objects: 63643, done. remote: Counting objects: 100% (63643/63643), done. remote: Compressing objects: 100% (27437/27437), done. remote: Total 63643 (delta 52300), reused 43882 (delta 36038) Receiving objects: 100% (63643/63643), 14.39 MiB | 5.97 MiB/s, done. Resolving deltas: 100% (52300/52300), done. Submodule 'jimtcl' ( https://repo.or.cz/jimtcl.git ) registered for path 'jimtcl' Submodule 'src/jtag/drivers/libjaylink' ( https://repo.or.cz/libjaylink.git ) registered for path 'src/jtag/drivers/libjaylink' Submodule 'tools/git2cl' ( https://repo.or.cz/git2cl.git ) registered for path 'tools/git2cl' Cloning into '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' ... fatal: unable to access 'https://repo.or.cz/jimtcl.git/' : Failed to connect to repo.or.cz port 443: Connection timed out fatal: clone of 'https://repo.or.cz/jimtcl.git' into submodule path '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' failed Failed to clone 'jimtcl' . Retry scheduled Cloning into '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/src/jtag/drivers/libjaylink' ... fatal: unable to access 'https://repo.or.cz/libjaylink.git/' : Failed to connect to repo.or.cz port 443: Connection timed out fatal: clone of 'https://repo.or.cz/libjaylink.git' into submodule path '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/src/jtag/drivers/libjaylink' failed Failed to clone 'src/jtag/drivers/libjaylink' . Retry scheduled Cloning into '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/tools/git2cl' ... fatal: unable to access 'https://repo.or.cz/git2cl.git/' : Failed to connect to repo.or.cz port 443: Connection timed out fatal: clone of 'https://repo.or.cz/git2cl.git' into submodule path '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/tools/git2cl' failed Failed to clone 'tools/git2cl' . Retry scheduled Cloning into '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' ... fatal: unable to access 'https://repo.or.cz/jimtcl.git/' : Failed to connect to repo.or.cz port 443: Connection timed out fatal: clone of 'https://repo.or.cz/jimtcl.git' into submodule path '/Host/home/kristof/Work/openocd-0.10.0-14/openocd.git/jimtcl' failed Failed to clone 'jimtcl' a second time, aborting I've tried to build OpenOCD twice today, and got the same error each time. Is this a temporary hiccup, or some URL that is pointing to something that moved? Thank you very much :-) Kind greetings, Kristof Mulier ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
