Hi @Liviu Ionescu and @Tommy Murphy,
Sorry for my late reply.
The way I attempt to execute OpenOCD
=====================================
In my last e-mail, I told you that I executed OpenOCD after the build
without specifying *how* exactly. My apologies for that. So here is what
I did:
1. I copied everything from ~/Work/openocd-0.10.0-14/deploy/ into
another folder:
$ cd ~/Work/openocd-0.10.0-14/deploy
$ cp -R * /media/sf_ubuntu
$ cd /media/sf_ubuntu
2. I extracted the zipped file "xpack-openocd-0.10.0-14-linux-x64.tar.gz"
in that folder. The extraction itself I did from the standard Ubuntu
file explorer (so not from the terminal).
3. I navigate into the extracted folder, and execute OpenOCD from there:
$ cd
/media/sf_ubuntu/xpack-openocd-0.10.0-14-linux-x64/xpack-openocd-0.10.0-14/bin
$ ./openocd --version
./openocd: error while loading shared
libraries: libusb-0.1.so.4: cannot open
shared object file: No such file or
directory
Tommy Murphy's build
=====================
So @Tommy Murphy, you successfully built OpenOCD (with the last
three lines in the build script uncommented), and it just works?
Could it be that my Ubuntu version is the culprit (I'm using
Ubuntu 20.04.1 LTS). Although this shouldn't matter, because
eventually the build happens in Docker...
Suggestions about the how-to-build pages
=========================================
@Liviu Ionescu, I also don't know how I screw things up. It seems
like the heavens don't want me to build OpenOCD...
Based on your build instructions, I wrote a guide (mainly for my own
use) on how to build OpenOCD:
https://new.embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build
In this guide, I literally documented every single step. I made that
guide a couple of months ago, because I've had so many troubles with building
OpenOCD in the past. I took the "write everyting down" approach, like really
every single click. It's as if I'm explaining to my grandmom how to do it.
Somehow I thought this guide would save me from further issues, which it did as
long as I only tested the Windows executables. Trouble started when I tested the
Linux executable a couple of days ago.
So my only suggestion: write it as if you're explaining it to your grandmom
(hopefully she is not a computer scientist).
I'm really thankful for all the efforts you made and still make!
I'll make another donation, because you're my OpenOCD hero!
Kind regards,
Kristof Mulier
----- Oorspronkelijk bericht -----
Van: "Liviu Ionescu" <i...@livius.net>
Aan: "Tommy Murphy" <tommy_mur...@hotmail.com>
Cc: "kristof mulier" <kristof.mul...@telenet.be>, "johan" <jo...@embeetle.com>,
"matic" <ma...@embeetle.com>, "openocd-devel"
<openocd-devel@lists.sourceforge.net>
Verzonden: Maandag 31 augustus 2020 14:14:20
Onderwerp: Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.
> On 31 Aug 2020, at 15:08, Tommy Murphy <tommy_mur...@hotmail.com> wrote:
>
> ... the xPack project pages
with all those pages, it seems that people always find creative ways to mess
things up, so my conclusion is that those pages need improvements.
I'm open to any suggestions.
Kristof? what is wrong with those pages, such that you could not make it?
Liviu
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
