From: David Gibson <david@gibson.dropbear.id.au>
To: devicetree-compiler@vger.kernel.org
Subject: Device Tree Compiler v1.7.2
Date: Wed, 6 Nov 2024 14:23:00 +1100 [thread overview]
Message-ID: <ZyrhFOUYIoR2xpnQ@zatzit> (raw)
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
It hasn't been that long since v1.7.1, but several people have
reported a compile breakage with swig 4.3.0. Building this release,
primarily so distros can easily get the version with the fix.
As usual, the git tree can be had from:
git://git.kernel.org/pub/scm/utils/dtc/dtc.git
and tarballs can be had from:
https://mirrors.edge.kernel.org/pub/software/utils/dtc/
DTC 1.7.2
Changes since v1.7.1 include:
* Build
- Fix automatic dependency handling for paths with spaces in them
- Fix to allow compilation with swig 4.3.0
- Disable pointless warnings on swig generated code
* fdtoverlay
- Improve error message with missing /__symbols__
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-11-06 3:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZyrhFOUYIoR2xpnQ@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.