<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/blocktrron/include, branch master</title>
<subtitle>Staging tree of David Bauer</subtitle>
<id>https://git.openwrt.org/openwrt/staging/blocktrron/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/blocktrron/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/'/>
<updated>2025-11-12T11:11:15Z</updated>
<entry>
<title>prereq-build: add Python 3.13 support</title>
<updated>2025-11-12T11:11:15Z</updated>
<author>
<name>Kacper Ludwinski</name>
</author>
<published>2025-11-10T00:48:19Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=ba041eb451597d5b00ba55a80d7ff4fd262760f7'/>
<id>urn:sha1:ba041eb451597d5b00ba55a80d7ff4fd262760f7</id>
<content type='text'>
Add support for Python version 3.13 to include/prereq-build.mk.
One of the reasons for this change is that
Ubuntu 25.04 ships with Python 3.13 as default version.
Let's support it.

Signed-off-by: Kacper Ludwinski &lt;kacper@ludwinski.dev&gt;
Link: https://github.com/openwrt/openwrt/pull/20735
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>openssl: add MODULES_DIR MACRO for provider</title>
<updated>2025-11-11T22:58:54Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2025-11-11T22:58:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=b29cf08a1eb6af799b2bdaf5cf655532b238d2eb'/>
<id>urn:sha1:b29cf08a1eb6af799b2bdaf5cf655532b238d2eb</id>
<content type='text'>
Add MODULES_DIR MACRO for provider useful if the relevant package
require to define the default OpenSSL MODULES_PATH.

Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>toplevel.mk: use relative path for feeds/base symlink</title>
<updated>2025-11-10T14:20:34Z</updated>
<author>
<name>Andy Chiang</name>
</author>
<published>2025-10-04T10:38:41Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=631d535282a39f2d6a440b27f211a7678916f525'/>
<id>urn:sha1:631d535282a39f2d6a440b27f211a7678916f525</id>
<content type='text'>
Currently, feeds/base is created as an absolute symlink to $(TOPDIR)/package.
If the OpenWrt source tree is copied to another location for building (while keeping the old tree), the symlink will still point to the package directory in the old tree.
Using a relative symlink ensures that feeds/base always points to the package directory within the current OpenWrt source tree, improving portability and avoiding incorrect links.

Signed-off-by: Andy Chiang &lt;AndyChiang_git@outlook.com&gt;
Link: https://github.com/openwrt/openwrt/pull/20297
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>include: download.mk: do not check PKG_MIRROR_HASH when set to "skip"</title>
<updated>2025-11-07T11:25:42Z</updated>
<author>
<name>Matthias Franck</name>
</author>
<published>2025-11-05T13:43:53Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=2df73702c52b2dec7debb8b618d556385cf10f70'/>
<id>urn:sha1:2df73702c52b2dec7debb8b618d556385cf10f70</id>
<content type='text'>
In commit 042996b46bd41292ef1fa2d58e3b824a547f4c55 compilation of git repos is made to fail when PKG_MIRROR_HASH is not correct.

It looks like it was forgotten that in openwrt there is a posibility to set the PKG_MIRROR_HASH to "skip".
In this case the hash check should not be performed and compilation should continue as expected.

This is especially very usefull when doing local testing and development with git repos.

Signed-off-by: Matthias Franck &lt;matthias.franck@softathome.com&gt;
Link: https://github.com/openwrt/openwrt/pull/20655
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>cmake: set CMAKE_FIND_ROOT_PATH_MODE_PROGRAM=NEVER</title>
<updated>2025-11-05T15:57:51Z</updated>
<author>
<name>Eneas U de Queiroz</name>
</author>
<published>2025-06-20T13:18:58Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=e4956451353b744fe15312366a09b0d17832332d'/>
<id>urn:sha1:e4956451353b744fe15312366a09b0d17832332d</id>
<content type='text'>
According to CMake documentation[1]:

  [CMAKE_FIND_ROOT_PATH] is a list of directories that contain the
  target environment.

  [CMAKE_FIND_ROOT_PATH_MODE_PROGRAM] sets the default behavior for the
  find_program command.

  In most cases, find_program is used to search for an executable which
  will then be executed, e.g. using execute_process or
  add_custom_command. So in most cases an executable from the build host
  is required, so setting CMAKE_FIND_ROOT_PATH_MODE_PROGRAM to NEVER is
  normally preferred.

Since CMAKE_FIND_ROOT_PATH is set to the target staging dir, and the
toolchain root dir, it will find target programs before the host ones.

An example of this problem is if you try to build antiblock from the
packages feed after llvm from the video feeds is built.  Antiblock will
search for clang-format, pickup the target version, and fail to build.

Signed-off-by: Eneas U de Queiroz &lt;cotequeiroz@gmail.com&gt;

[1] https://cmake.org/cmake/help/book/mastering-cmake/chapter/Cross%20Compiling%20With%20CMake.html
Link: https://github.com/openwrt/openwrt/pull/20656

Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>build: Add _FORTIFY_SOURCE=3 support</title>
<updated>2025-10-25T23:43:01Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2025-10-05T21:30:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=93f86627c45a03c2c100e54f5ef006487af3e6e3'/>
<id>urn:sha1:93f86627c45a03c2c100e54f5ef006487af3e6e3</id>
<content type='text'>
Add support for _FORTIFY_SOURCE level 3.

This is supported with glibc and with musl libc.

Link: https://github.com/openwrt/openwrt/pull/20313
Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>image: move mkits.sh outside lock section</title>
<updated>2025-10-23T16:14:01Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2025-10-22T00:45:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=5a42ed1138ae0244aff79560fe77cfab8aff6e7f'/>
<id>urn:sha1:5a42ed1138ae0244aff79560fe77cfab8aff6e7f</id>
<content type='text'>
As mkits.sh only generates the relevant DTS for mkimage and is
specific for the building image, we can move it outside the locked
section as it doesn't do any operation that can be used concurrently by
others.

This won't have any real impact but clean the code making it clear what
needs to be protected and what can be executed concurrently.

Link: https://github.com/openwrt/openwrt/pull/20492
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>scripts/mkits.sh: move out .pagesync generation for RootFS blob</title>
<updated>2025-10-23T16:14:01Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2025-10-23T13:31:46Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=c70894c855e54624b918ab50c9afa53301c462d4'/>
<id>urn:sha1:c70894c855e54624b918ab50c9afa53301c462d4</id>
<content type='text'>
It's expected the mkits.sh script to generate only the relevant DTS
entry and have all the blob already prepared to use for mkimage.

This is not the case for the RootFS case where the script generates a
.pagesync with the dd command.

To better handle this, drop the dd command and instead error out if the
.pagesync blob is not found if RootFS is used.

Adapt the generic fit build in image-commands.mk to call the dd for
.pagesync right before mkits.sh.

Link: https://github.com/openwrt/openwrt/pull/20492
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>image: fix race between mkits.sh and mkimage in .itb squashfs generation</title>
<updated>2025-10-23T16:14:00Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2025-10-22T00:17:25Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=3de1bbd5aeb542de9a4b20eff0f6bbf1767fd6b9'/>
<id>urn:sha1:3de1bbd5aeb542de9a4b20eff0f6bbf1767fd6b9</id>
<content type='text'>
With further investigation it was found a race in generating .itb images
that include a RootFS caused by the mkits.sh and the mkimage.

Due to the fact that mkits.sh generates a .pagesync image of the passed
rootfs, it can happen that, concurrently, mkimage can be called at the
same time mkits.sh is creating another .pagesync for the same rootfs.

This cause mkimage to use an half made rootfs.pagesync creating a
corrupted image.

To address this, also protect the mkimage with the same lock used for
mkits.sh preventing any kind of concurrent usage/generation of the
rootfs.pagesync blob

Fixes: 52cc9d82f113 ("kernel: rework Initramfs locking logic")
Link: https://github.com/openwrt/openwrt/pull/20492
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>build: handle --root feeds script feature</title>
<updated>2025-10-20T11:50:15Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2025-10-19T18:43:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=330d17f52d3cbe50802101966368c45e1d822453'/>
<id>urn:sha1:330d17f52d3cbe50802101966368c45e1d822453</id>
<content type='text'>
Rework the package SOURCE entry handling to account for the --root feeds
script feature.

Move the SOURCE entry string manipulation logic outside package-defaults.mk
in package.mk and limit only to non DUMP scenario to not pollute the .mk
too much.

Restructure the previous logic and add a new additional condition.
If we detect the package comes from a feed, replace any feed path that
have the _root prefix to the feed name with the non-root variant (the
feeds script create a symbolic link to it) and point the package SOURCE
entry to what the symbolic link points to.

Example:
Feed link: feeds/base_root/package -&gt; feeds/base
Package: feeds/base_root/package/system/uci -&gt; feeds/base/system/uci

Link: https://github.com/openwrt/openwrt/pull/20459
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
</feed>
