For quicker reference here are both patches:
========================================
diff --git a/configure.ac b/configure.ac
index 6e60733..d6e49d8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -556,7 +556,7 @@ AS_IF([test "x$build_buspirate" = "xyes"], [
AS_IF([test "x$use_internal_jimtcl" = "xyes"], [
AS_IF([test -f "$srcdir/jimtcl/configure.ac"], [
- AX_CONFIG_SUBDIR_OPTION([jimtcl], [--disable-install-jim
--with-ext="eventloop array clock regexp stdlib tclcompat"
--without-ext="default"])
+ AX_CONFIG_SUBDIR_OPTION([jimtcl], [--disable-install-jim
--with-ext="eventloop array clock regexp stdlib tclcompat aio binary exec file
glob" --without-ext="default"])
], [
AC_MSG_ERROR([jimtcl not found, run git submodule init and git submodule
update.])
])
diff --git a/jimtcl b/jimtcl
--- a/jimtcl
+++ b/jimtcl
@@ -1 +1 @@
-Subproject commit a9bf5975fd0f89974d689a2d9ebd0873c8d64787
+Subproject commit a9bf5975fd0f89974d689a2d9ebd0873c8d64787-dirty
========================================
diff --git a/auto.def b/auto.def
index fc32b68..a692eb7 100644
--- a/auto.def
+++ b/auto.def
@@ -286,17 +286,17 @@ dict set extdb attrs {
# check=[expr] expression to evaluate to determine if the extension can be used
# libdep=list of 'define' symbols for dependent libraries
dict set extdb info {
- binary { dep pack }
+ binary { dep {package pack} }
exec { check {([have-feature vfork] && [have-feature waitpid]) ||
[have-feature system]} }
- glob { dep readdir }
+ glob { dep {package readdir} }
load { check {[have-feature dlopen-compat] ||
[cc-check-function-in-lib dlopen dl]} libdep lib_dlopen }
mk { check {[check-metakit]} libdep lib_mk }
namespace { dep nshelper }
posix { check {[have-feature waitpid]} }
readdir { check {[have-feature opendir]} }
readline { pkg-config readline check {[cc-check-function-in-lib readline
readline]} libdep lib_readline}
- rlprompt { dep readline }
- tree { dep oo }
+ rlprompt { dep {package readline} }
+ tree { dep {package oo} }
sdl { pkg-config SDL_gfx check {[cc-check-function-in-lib
SDL_SetVideoMode SDL] && [cc-check-function-in-lib rectangleRGBA SDL_gfx]}
libdep {lib_SDL_SetVideoMode lib_rectangleRGBA}
}
@@ -304,7 +304,7 @@ dict set extdb info {
sqlite3 { pkg-config sqlite3 check {[cc-check-function-in-lib
sqlite3_prepare_v2 sqlite3]} libdep lib_sqlite3_prepare_v2 }
zlib { pkg-config zlib check {[cc-check-function-in-lib deflate z]}
libdep lib_deflate }
syslog { check {[have-feature syslog]} }
- tree { dep oo }
+ tree { dep {package oo} }
win32 { check {[have-feature windows]} }
}
========================================
From: [email protected] [mailto:[email protected]] On Behalf Of Mark Odell
Sent: Friday, March 24, 2017 6:33 AM
To: Frazier, Mitch [AUTOSOL/FLMC/US]
Cc: [email protected]
Subject: Re: [OpenOCD-devel] TCL open command not working?
Good to know. Thank you. I thougt I was going crazy. Yes, I'm using git master
pulls so v0.10-dev.
On Wed, Mar 22, 2017 at 7:09 PM, <[email protected]> wrote:
Assuming you're using OpenOCD 0.10.0 this looks like the same issue that I ran
into that's described in the mailing list exchange with the subject:
"[OpenOCD-devel] missing tcl commands in 0.10.0". There is a patch in Gerrit
(http://openocd.zylin.com/4001) that addresses it, but it doesn't quite fix it.
My last email to the mailing list related to the above subject contains a
patch which along with the Gerrit patch referenced above fixes the problem.
From: Mark Odell [mailto:[email protected]]
Sent: Wednesday, March 22, 2017 8:03 AM
To: [email protected]
Subject: [OpenOCD-devel] TCL open command not working?
I recently noticed that my TCL file is now failing to log my internal debug
statements to a file. I tracked it down to this:
global g_logfh
set fname "/tmp/usertcl-$BOARD-$DAP_SERNO.log"
if {[catch {set g_logfh [open $fname w]} errmsg]} {
set g_logfh -1
}
I'm catching the error but the open call is failing stating, 'invalid command
name "open"'. This used to work and I haven't changed my TCL code in ages. I
didn't notice when (OpenOCD version) it started failing but I think that TCL's
open command should work.
Thoughts?
- Mark
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
