Your message dated Tue, 01 Sep 2026 18:51:14 +0000
with message-id <[email protected]>
and subject line Bug#1146077: fixed in openocd 0.12.0-4
has caused the Debian Bug report #1146077,
regarding openocd: FTBFS with jimtcl 0.84
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1146077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1146077
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openocd
Version: 0.12.0-3
Severity: important
Tags: ftbfs, patch
Affects: jimtcl
Dear Maintainer,
I am planing to upload jimtcl 0.84-2 to unstable soon and request one
transition from 0.83 to 0.84. Rebuild openocd with the jimtcl 0.84-1 but
will get:
```
src/helper/log.c: In function 'log_puts':
src/helper/log.c:99:11: warning: assignment discards 'const' qualifier from
pointer target type [-Wdiscarded-qualifiers]
99 | f = strrchr(file, '/');
| ^
src/helper/command.c: In function 'jimcmd_is_proc':
src/helper/command.c:51:19: error: 'Jim_Cmd' has no member named 'isproc'
51 | return cmd->isproc;
| ^~
src/helper/command.c: In function 'jimcmd_is_oocd_command':
src/helper/command.c:56:20: error: 'Jim_Cmd' has no member named 'isproc'
56 | return !cmd->isproc && cmd->u.native.cmdProc ==
jim_command_dispatch;
| ^~
src/helper/command.c: In function 'jimcmd_privdata':
src/helper/command.c:61:19: error: 'Jim_Cmd' has no member named 'isproc'
61 | return cmd->isproc ? NULL : cmd->u.native.privData;
| ^~
libtool: link: ar cr src/xsvf/.libs/libxsvf.a src/xsvf/xsvf.o
libtool: link: ranlib src/xsvf/.libs/libxsvf.a
```
Upstream has one commit[0] to fix the build issue and I can confirm that
it works on Debian here also.
So once I upload jimtcl 0.84-2 to unstable, could you have a look at
this?
[0]: https://review.openocd.org/c/openocd/+/8956
--
Regards,
--
Bo YU
From fe0080478b9e76a4b6b64186b7b705726ac55848 Mon Sep 17 00:00:00 2001
From: Antonio Borneo <[email protected]>
Date: Sat, 28 Sep 2024 17:58:51 +0200
Subject: [PATCH] jimtcl: fix build with jimtcl master branch
Current jimtcl release 0.83 has been tagged on 2024-08-28 and the
new 0.84 is on the way.
The change [1] merged in jimtcl branch 'master' for 0.84 breaks
the build of OpenOCD.
OpenOCD releases are not frequent and jimtcl is now by default an
external build dependency. The release of jimtcl 0.84 could force
OpenOCD to deliver a fix release to support it.
Anticipate the change [1] by detecting it at compile time, without
relying on jimtcl version, and providing an alternative code.
Link: https://github.com/msteveb/jimtcl/commit/5669e84aad22 [1]
Change-Id: I61bf100d447083258aea222aaf15608b7cbe2e57
Signed-off-by: Antonio Borneo <[email protected]>
Reviewed-on: https://review.openocd.org/c/openocd/+/8956
Tested-by: jenkins
Reviewed-by: Andrzej Sierżęga <[email protected]>
---
--- a/src/helper/command.c
+++ b/src/helper/command.c
@@ -48,17 +48,22 @@
/* set of functions to wrap jimtcl internal data */
static inline bool jimcmd_is_proc(Jim_Cmd *cmd)
{
+#if defined(JIM_CMD_ISPROC)
+ // JIM_VERSION >= 84
+ return cmd->flags & JIM_CMD_ISPROC;
+#else
return cmd->isproc;
+#endif
}
bool jimcmd_is_oocd_command(Jim_Cmd *cmd)
{
- return !cmd->isproc && cmd->u.native.cmdProc == jim_command_dispatch;
+ return !jimcmd_is_proc(cmd) && cmd->u.native.cmdProc == jim_command_dispatch;
}
void *jimcmd_privdata(Jim_Cmd *cmd)
{
- return cmd->isproc ? NULL : cmd->u.native.privData;
+ return jimcmd_is_proc(cmd) ? NULL : cmd->u.native.privData;
}
static void tcl_output(void *privData, const char *file, unsigned line,
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: openocd
Source-Version: 0.12.0-4
Done: Jonathan McDowell <[email protected]>
We believe that the bug you reported is fixed in the latest version of
openocd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan McDowell <[email protected]> (supplier of updated openocd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 01 Sep 2026 19:38:35 +0100
Source: openocd
Architecture: source
Version: 0.12.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Packaging Team
<[email protected]>
Changed-By: Jonathan McDowell <[email protected]>
Closes: 1146077
Changes:
openocd (0.12.0-4) unstable; urgency=medium
.
* Fix build with jimtcl 0.84. Thanks to Bo YU for pulling out the upstream
patch. (Closes: #1146077)
* Fix Build-Depends / Build-Depends-Arch up
Checksums-Sha1:
6ca124afdc2b9b2221a3ae81a0851fd27208d2cd 1774 openocd_0.12.0-4.dsc
10f78632d35d723d022af5ee9ba51dd81222518e 17464 openocd_0.12.0-4.debian.tar.xz
0c7cd2d356bfe59fda597b9c4dc47ccf92c7ab0f 8145 openocd_0.12.0-4_amd64.buildinfo
Checksums-Sha256:
1eb6f2e49bd70453a1f788f202d7d2deb9f9675a2a3c8efe1bdf65e81d1f6b41 1774
openocd_0.12.0-4.dsc
1f87ae9b8fc293d402ce4ece769be1c0d9ded59a3f6a8f4e47140123f3a994de 17464
openocd_0.12.0-4.debian.tar.xz
f24f7a3a04e0d6b3e3ba883fdd8c7b47b1aef430a2f276c1d3dd9dc6ecb36c39 8145
openocd_0.12.0-4_amd64.buildinfo
Files:
6fb7a6abcbafef7d0ff8318fd28b0c54 1774 embedded optional openocd_0.12.0-4.dsc
1b76605304941356e81ba9ecc0492969 17464 embedded optional
openocd_0.12.0-4.debian.tar.xz
1204c972c8284365d966ebc975057af5 8145 embedded optional
openocd_0.12.0-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQSAYP1ALvrBQa1odmMPwJuF4mk8PAUCapcdWgAKCRAPwJuF4mk8
PDBTAQD4qizKzZcZwGQt87m6yP4mxgsBpQJ2+uXrnqx12ag2MAEA2irdqxq3L/oy
Ssm9OgPWDRJFfaV8q7XWIF1rlA4segU=
=pT5g
-----END PGP SIGNATURE-----
pgpJ2DK61cVaR.pgp
Description: PGP signature
--- End Message ---
