Hi @Liviu, Hi @Tommy, I'm following the guide(s) on the xPack website. However, I got stuck when executing the fourth command on the Prerequisites page (see https://xpack.github.io/xbb/prerequisites/): $ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $( lsb_release -cs ) stable" This is the output I get: Hit:1 http://be.archive.ubuntu.com/ubuntu eoan InRelease Hit:2 http://be.archive.ubuntu.com/ubuntu eoan-updates InRelease Hit:3 http://be.archive.ubuntu.com/ubuntu eoan-backports InRelease Get:4 http://security.ubuntu.com/ubuntu eoan-security InRelease [97,5 kB] Ign:5 https://download.docker.com/linux/ubuntu eoan InRelease Err: 6 https://download.docker.com/linux/ubuntu eoan Release 404 Not Found [IP: 13.225.38.15 443] Reading package lists... Done E: The repository 'https://download.docker.com/linux/ubuntu eoan Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. What should I do?
--------------- By the way, I note down every single step of my journey to get OpenOCD compiled on this page: https://forum.embeetle.com/t/building-openocd/137 this way - if the OpenOCD xPack build succeeds - I've got a trace back. --------------- Kind greetings, Kristof Mulier Van: "Tommy Murphy" <tommy_mur...@hotmail.com> Aan: "kristof mulier" <kristof.mul...@telenet.be>, "Liviu Ionescu" <i...@livius.net> Cc: "openocd-devel" <openocd-devel@lists.sourceforge.net> Verzonden: Maandag 20 januari 2020 21:33:33 Onderwerp: Re: [OpenOCD-devel] Compliance with OpenOCD license The instructions definitely work on Ubuntu. I've been using Ubuntu 18 lately. Other distros probably work as well. Don't forget to read the "prerequisite" instructions for installing docker. Once that's done it should be trivial to pull and run the build process. As I mentioned earlier if you want to build from the upstream master openocd repo rather than Liviu's snapshots then you may need to pass additional options to build.sh or maybe edit even edit the scripts. I can't remember offhand but I could check later if necessary. Best to pipeclean the build process as is first before changing anything in any case. From: kristof.mul...@telenet.be <kristof.mul...@telenet.be> Sent: Monday, January 20, 2020 7:58:25 PM To: Liviu Ionescu <i...@livius.net> Cc: Tommy Murphy <tommy_mur...@hotmail.com>; openocd-devel <openocd-devel@lists.sourceforge.net> Subject: Re: [OpenOCD-devel] Compliance with OpenOCD license Hi @Liviu Ionescu, > The scripts have lots of configuration environment > variables, if you want to build a more recent version, > you need to tweak them. > [..] Uh oh... I have not even the foggiest idea how to "tweak" your build scripts. To be honest, I was hoping to simply run the build script and watch the OpenOCD Windows binaries showing up magically :-) Unfortunately it doesn't seem to be that simple. > However please note that the scripts are not specific > for generating production binaries, which have certain > requirements, and are less suitable for experimenting > with builds. When I'm "experimenting with a build" this is what I do: I connect the microcontroller and the probe. Then I start OpenOCD and feed it with the right config files. If OpenOCD connects to the chip and is able to flash a firmware, I consider the experiment to be successful. So for this kind of "experiments", a "production binary" is perfectly fine. I don't need a "debug binary". Many thanks for your help :-) ----- Oorspronkelijk bericht ----- Van: "Liviu Ionescu" <i...@livius.net> Aan: "kristof mulier" <kristof.mul...@telenet.be> Cc: "Tommy Murphy" <tommy_mur...@hotmail.com>, "openocd-devel" <openocd-devel@lists.sourceforge.net> Verzonden: Maandag 20 januari 2020 20:46:23 Onderwerp: Re: [OpenOCD-devel] Compliance with OpenOCD license > On 20 Jan 2020, at 21:36, kristof.mul...@telenet.be wrote: > > ... I conclude this particular OpenOCD executable was built last summer. That's correct. Since OpenOCD has no release schedule, I have no idea when to make xPack releases. > .. I suppose your > instructions to build the OpenOCD xPack will run smoothly in Ubuntu? Yes. The scripts have lots of configuration environment variables, if you want to build a more recent version, you need to tweak them. There is also a script to build native binaries, intended for debug sessions, but I'm not sure you can generate Windows binaries. However please note that the scripts are not specific for generating production binaries, which have certain requirements, and are less suitable for experimenting with builds. After playing with the scripts you'll probably prefer to use the already made binaries. FYI, I plan for a new release shortly. Regards, Liviu
_______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
