Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39577 - [openocd] build fails
Attached to Project:
Community Packages
Opened by Joel Teichroeb (klusark) - Saturday, 22 March 2014, 00:08 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 22 April 2014, 15:28 GMT
Opened by Joel Teichroeb (klusark) - Saturday, 22 March 2014, 00:08 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 22 April 2014, 15:28 GMT
|
DetailsDescription:
checking for vasprintf... yes checking whether to build a release... yes checking whether to build Doxygen as HTML... yes checking whether to build Doxygen as PDF... no checking whether to enable verbose JTAG I/O messages... no checking whether to enable verbose USB I/O messages... no checking whether to enable verbose USB communication messages... no checking whether to enable malloc free space logging... no checking whether to enable ZY1000 minidriver... no checking whether to enable dummy minidriver... no checking whether standard drivers can be built... yes checking Build & Link with libftdi...... configure: error: Cannot build & run test program using libftdi ==> ERROR: A failure occurred in build(). Aborting... Steps to reproduce: sudo extra-x86_64-build |
This task depends upon