On Tue, Sep 1, 2020 at 6:12 PM Liviu Ionescu wrote:
>
> > On 1 Sep 2020, at 12:57, Xiaofan Chen wrote:
> >
> > Interesting issue.
> >
> > Just want to check whether you are pulling the latest libusb, hidapi
> > and libftdi release.
>
> Yes, generally I try to use the latest available releases.
>
> On 1 Sep 2020, at 12:57, Xiaofan Chen wrote:
>
> Interesting issue.
>
> Just want to check whether you are pulling the latest libusb, hidapi
> and libftdi release.
Yes, generally I try to use the latest available releases.
> BTW, for libusb and hidapi, the git head may have quite some
You can see here what lib versions and repos that Liviu is using:
https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/scripts/common-versions-source.sh#L37
https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/scripts/common-libs-functions-source.sh#L16
Interesting issue.
Just want to check whether you are pulling the latest libusb, hidapi
and libftdi release.
BTW, for libusb and hidapi, the git head may have quite some fixes as
well but no new release yet.
libusb: now we prefer github than Sourceforge
https://github.com/libusb/libusb/releases
> On 1 Sep 2020, at 10:50, kristof.mul...@telenet.be wrote:
>
> Beware of the location where you unzip the build output.
> I copied the build output to a folder on my Ubuntu VM that
> is shared with the Windows host OS. Unzipping it there -
> even though it's done on the Ubuntu VM - kills all
Hi,
To everyone who is following the e-mail chain between me,
Liviu Ionescu and Tommy Murphy about the build failure:
the story came to and end.
We have a conclusion:
Beware of the location where you unzip the build output.
I copied the build output to a folder on my Ubuntu VM that
is shared
> 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...
I don't think so.
I just did a build of the linux 64 bit openocd on Ubuntu 20.04.1 and it went
fine and ldd -v doesn't show
openocd-devel"
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 wrote:
>
> ... the xPack project pages
with all those pages, it seems that people always find creat
> On 31 Aug 2020, at 15:08, Tommy Murphy 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
> Again my sincere thanks to all of you (Liviu Ionescu, Tommy Murphy, ...) that
> are
> helping people like me to build OpenOCD for Windows/Linux/Mac.
>
> Kind regards,
> Kristof Mulier
Thanks but I am really just restating what Liviu already says on the xPack
project pages so not actually
> On 31 Aug 2020, at 14:47, Tommy Murphy wrote:
>
> user@cockatoo:~/Downloads/xpack-openocd-0.10.0-14/bin$ ldd openocd
> linux-vdso.so.1 (0x7ffd1695f000)
> libusb-0.1.so.4 =>
> /home/user/Downloads/xpack-openocd-0.10.0-14/bin/./libusb-0.1.so.4
> (0x7f21f828a000)
> libftdi1.so.2 =>
I just did a full rebuild of everything from the upstream openocd repo/HEAD
(i.e. last three lines of defs-source.sh uncommented).
The build went fine as usual.
I then did this:
user@cockatoo:~$ cd ~/Downloads
user@cockatoo:~/Downloads$ tar -xzvf
> On 31 Aug 2020, at 13:43, kristof.mul...@telenet.be wrote:
>
> First I navigate to the
> folder where the OpenOCD executable is
since none of the libraries are found by ldd, you're probably not navigating to
the correct folder. it should be
ss I'm
doing
something wrong myself here).
Again my sincere thanks to all of you (Liviu Ionescu, Tommy Murphy, ...) that
are
helping people like me to build OpenOCD for Windows/Linux/Mac.
Kind regards,
Kristof Mulier
Van: "Tommy Murphy"
Aan: "Liviu Ionescu"
Cc: "
-devel] Missing libusb shared object file in xPack build.
> On 30 Aug 2020, at 15:36, Tommy Murphy wrote:
>
> ... sudo rm -rf ~/Work to clean all downloads off
cleaning the Work/cache folder is not necessary, on the contrary.
regards,
Liviu
__
> On 30 Aug 2020, at 15:36, Tommy Murphy wrote:
>
> ... sudo rm -rf ~/Work to clean all downloads off
cleaning the Work/cache folder is not necessary, on the contrary.
regards,
Liviu
___
OpenOCD-devel mailing list
: "kristof mulier"
Cc: "Liviu Ionescu" , "johan" , "matic"
, "openocd-devel"
Verzonden: Zondag 30 augustus 2020 14:38:38
Onderwerp: Re: [OpenOCD-devel] Missing libusb shared object file in xPack
build.
"Repo outages" not "dro
"Repo outages" not "drop outages".
From: Tommy Murphy
Sent: Sunday, August 30, 2020 1:36:33 PM
To: kristof.mul...@telenet.be
Cc: Liviu Ionescu ; johan ; matic
; openocd-devel
Subject: Re: [OpenOCD-devel] Missing libusb shared object file in
: [OpenOCD-devel] Missing libusb shared object file in xPack build.
Hi @Tommy Murphy,
Thank you very much for sharing the precise commands
you enter to build OpenOCD :-)
I've tried this morning, but got the following problem:
Downloading "libusb-win32-src-1.2.6.0.zip" from
ourceforge page is down?
I'll try again this afternoon.
Kind regards,
Kristof Mulier
Van: "Tommy Murphy"
Aan: "Liviu Ionescu" , "kristof mulier"
Cc: "johan" , "matic" , "openocd-devel"
Verzonden: Zaterdag 29 augustus 2020 21:36:25
> On 30 Aug 2020, at 13:09, kristof.mul...@telenet.be wrote:
>
> Downloading "libusb-win32-src-1.2.6.0.zip" from
>
> "http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-src-1.2.6.0.zip;...
> % Total% Received % Xferd Average Speed
ripts/build.sh --all
From: Liviu Ionescu
Sent: Saturday 29 August 2020 19:21
To: kristof.mul...@telenet.be
Cc: Tommy Murphy ; johan ; matic
; openocd-devel
Subject: Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.
> On 29 Aug 2020, at 21:18, kristof.mul...@telenet.
> On 29 Aug 2020, at 21:18, kristof.mul...@telenet.be wrote:
>
> ... I got it running properly
told you so!
> So what would change in these commands to achieve that? ... defs-source.sh'
> file (uncommenting the last three lines)? Or is it something else?
Keine Ahnung, I never used the
lijk bericht -
Van: "Liviu Ionescu"
Aan: "kristof mulier"
Cc: "Tommy Murphy" , "johan" ,
"matic" , "openocd-devel"
Verzonden: Zaterdag 29 augustus 2020 20:11:21
Onderwerp: Re: [OpenOCD-devel] Missing libusb shared object file in x
> On 29 Aug 2020, at 21:06, kristof.mul...@telenet.be wrote:
>
> does this pull the latest
> master branch from the official OpenOCD git repo before doing the build?
Negative, this is a production build that pulls a specific commit from my
openocd fork.
Once you have this running properly,
2020 19:59:41
Onderwerp: Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.
> On 29 Aug 2020, at 20:34, kristof.mul...@telenet.be wrote:
>
> Did you refer to this guide from Liviu:
> https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md
O
> On 29 Aug 2020, at 20:34, kristof.mul...@telenet.be wrote:
>
> Did you refer to this guide from Liviu:
> https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md
On a Ubuntu 20 VM, with curl, git and docker installed:
$ curl -L
...@telenet.be
Cc: johan ; matic ; openocd-devel
Subject: Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.
> On 29 Aug 2020, at 19:28, kristof.mul...@telenet.be wrote:
>
> What did I do wrong?
For one, you merged different Git repos. This shows that you are far from
unde
"
Cc: "johan" , "matic" , "openocd-devel"
Verzonden: Zaterdag 29 augustus 2020 19:23:34
Onderwerp: Re: [OpenOCD-devel] Missing libusb shared object file in xPack
build.
If you follow Liviu's build instructions to the letter everything will build
perfectly e
> 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
> 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"
Hi Liviu,
I'm indeed experimenting :-)
The reason I did those merges is because of this part in your guide (see
https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md)
Update git repos
=
To keep the development repository in sync with the original OpenOCD
> On 29 Aug 2020, at 19:28, kristof.mul...@telenet.be wrote:
>
> What did I do wrong?
For one, you merged different Git repos. This shows that you are far from
understanding the build process. :-(
> but I
> still want to be able to compile OpenOCD from the sources :-)
Sure, you're free to
Hi @Liviu,
Thank you for your quick reply.
I am thankful for the binaries you provide - I really do - but I
still want to be able to compile OpenOCD from the sources :-)
I didn't change the build scripts. Here are the steps I took.
FIRST TRY (29 Aug 2020, morning)
> On 29 Aug 2020, at 16:30, kristof.mul...@telenet.be wrote:
>
> $ ls -l
> total 4816
> -rwxrwx--- 1 root vboxsf 73232 Aug 29 14:14 libftdi1.so.2.4.0
> -rwxrwx--- 1 root vboxsf 22840 Aug 29 14:14 libhidapi-hidraw.so.0.0.0
> -rwxrwx--- 1 root vboxsf 992288 Aug 29
Hi Liviu (and other OpenOCD developers),
I just completed another build of OpenOCD on my Ubuntu VM. I'm following the
XPack guide from @Liviu Ionescu, see:
[ https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md |
36 matches
Mail list logo
