Problems found locating distfiles:
Package colorls: missing distfile ls.tar.gz
Package molden: missing distfile molden-4.6/molden4.6.tar.gz
Package softmaker-office-demo: missing distfile ofl06trial.tgz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
are replaced with .include "../../devel/readline/buildlink3.mk", and
USE_GNU_READLINE are removed,
* .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE
are replaced with .include "../../mk/readline.buildlink3.mk".
(misc/urjtag gettext-lib support)
This commit apparently fixes the PLIST problem on Linux.
Linux seems always gettext-lib available, while in
NetBSD (other *BSD ?) has it conditionally.
(As a side fix, add msgfmt to USE_TOOLS, thanks obache)
This commit adds gettext-lib support unconditionally.
Resulting some *.mo files are added to PLIST.
Add USB cable (with FTDI USB chip) support by
just including libftdi/buildlink3.mk. Now the number of
cables supported increased from 16 to 27.
(and Bump revision)
-add a "sync" option to the "dr" command which sets the next written
value to the last read one, seems useful to me to do least invasive
tests in a running system
-flush stdout on progress reports of the svf player (fixed differently
in the development branch upstream)
bump PKGREVISION
reduce the number of transactions which resulted in a wrong TDO
picked up under some circumstances
being here, quell a warning in the usbprog driver which only tells
us what we already know, and improve an error message
bump PKGREVISION
of the openwince-jtagtools (added features are ejtag support,
bsdl file import and svf player, probably more)
I've added a minimal driver for the "usbprog" adapter. It needs the
"usbprogJTAG" firmware which is not distributed in binary
by the developers but can be easily built with pkgsrc/cross/avr-gcc.
(There is some "openocd" firmware which looks similar, it might be
possible to make this work.)
Caution: The usbprog adapter does no Vref sampling but drives always 5V.
Make sure your taget device tolerates that. (I've tested with a PIC32
eval board.)
