I blindly updated with you suggested changes.
Search Criteria
Package Details: openocd-git-libftdi r132.8fd59d7-1
Package Actions
| Package Base: | openocd-git-libftdi |
|---|---|
| Description: | Debugging, in-system programming and boundary-scan testing for embedded target devices -using libftdi instead of ftd2xx |
| Upstream URL: | http://openocd.org/ |
| Category: | devel |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | nickoe |
| Maintainer: | nickoe |
| Last Packager: | nickoe |
| Votes: | 16 |
| First Submitted: | 2009-10-23 18:59 |
| Last Updated: | 2015-05-16 16:47 |
Latest Comments
Comment by nickoe
Comment by FreddieChopin
OK, while we're at it, a couple more things could be improved (;
1. "--enable-arm-jtag-ew" should be "--enable-armjtagew"
2. Some options worth adding:
--enable-aice
--enable-cmsis-dap
--enable-dummy
--enable-jtag_vpi
--enable-opendous
--enable-openjtag_ftdi
--enable-remote-bitbang
--enable-ti-icdi
--enable-ulink
--enable-usb-blaster-2
Comment by nickoe
Update with package function
Comment by FreddieChopin
When trying to install (with yaourt) I get this:
---
==> Building and installing package
==> ERROR: Missing package() function in /tmp/yaourt-tmp-freddie/aur-openocd-git-libftdi/./PKGBUILD
==> ERROR: Makepkg was unable to build openocd-git-libftdi.
---
It worked the last time I did the install, which was in November. Any help appreciated!
Comment by nickoe
I updated it to include both options.
Comment by nickoe
Could one safely use both options?
Comment by nickoe
Ok, I see that confiugure tells me, configure: error: The ft2232 driver is deprecated, use --enable-ftdi to build its replacement, or force the old driver with --enable-legacy-ft2232_libftdi
Is there any reason to use legacy and not just --enable-ftdi?
Comment by nickoe
@rami, what supercedes that driver since it is legacy now?
Comment by rami
In PKGBUILD:
--enable-ft2232_libftdi
has to be replaced by
--enable-legacy-ft2232_libftdi
Comment by nickoe
djvinz, thank you very much, I have now fixed it.
I like easy fixes :=)
Comment by djvinz
awesome package!
Just a type in the PKGBUILD:
--enable-usb_flaster_libftdi \
ought to be:
--enable-usb_blaster_libftdi \
thanks!
Comment by nickoe
Updated the package
- added the --enable-osbdm
- rmoved manual jimtcl build
- updated reference to automake
Comment by sergej
Please add --enable-osbdm, conflicts with jimtcl package.
Also automake workaround seems not needed anymore.
Comment by nickoe
@unkier: I added the stlink interface
@javsalgar: I have now made a temporary fix, to make it work. It has indeed something to do with automake. Now it works with automake 1.10. If you know how to make it work with the current automake, please inform me.
Comment by nickoe
@javsalgar: Yeah, I got the same problem, and I can't seem to find out how to solve. It happens when it tries to run ./bootstrap.
Comment by javsalgar
Does not compile, this error appears:
src/jtag/drivers/Makefile.am:8: `pkglibdir' is not a legitimate directory for `DATA'
src/jtag/stlink/Makefile.am:8: `pkglibdir' is not a legitimate directory for `DATA'
src/target/Makefile.am:167: `pkglibdir' is not a legitimate directory for `DATA'
Looks like it is an automake problem
Comment by unkier
add stlink please
Comment by nickoe
Added --disable-werror and a lot of interfaces.
Anonymous comment
looks like gcc 4.6 throws in lots of Wunused-but-set-variable errors.
Comment by nickoe
p5ycho: What is the point of --disable-werror? On my x86_64 machine it compiles without.
Where can i see the list of interfaces? I am having a hard time finding them.
Anonymous comment
needs a --disable-werror to compile.
also, please add more interfaces if possible? Take a look at the gentoo package for some inspiration :)
Comment by nickoe
tcl stuff fixed
Comment by lpjhjdh
tcl is required to build