> The key trick there is 'in the xpack-dev-tools/openocd Git repo'. Right, so I stay in the git repo that I cloned like this:
$ curl -L https://github.com/xpack-dev-tools/openocd-xpack/raw/xpack/scripts/git-clone.sh | bash $ cd ~/Downloads/openocd-xpack.git So the "merge from upstream/master" is simply the pull command, and I don't need to specifically clone the official OpenOCD repo (git://git.code.sf.net/p/openocd/code)? ----- Oorspronkelijk bericht ----- Van: "Liviu Ionescu" <i...@livius.net> Aan: "kristof mulier" <kristof.mul...@telenet.be> Cc: "openocd-devel" <openocd-devel@lists.sourceforge.net>, "johan" <jo...@embeetle.com>, "matic" <ma...@embeetle.com> Verzonden: Zaterdag 29 augustus 2020 18:45:08 Onderwerp: Re: Missing libusb shared object file in xPack build. > On 29 Aug 2020, at 19:42, kristof.mul...@telenet.be wrote: > > To keep the development repository in sync with the original OpenOCD > repository, in the xpack-dev-tools/openocd Git repo: The key trick there is 'in the xpack-dev-tools/openocd Git repo'. But this will probably not solve your problem. Use ldd -v to check dependencies. Regards, Liviu _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
