domoticz: disable LTO (for breaking the build)#29239
Open
ryjelsum wants to merge 1 commit intoopenwrt:masterfrom
Open
domoticz: disable LTO (for breaking the build)#29239ryjelsum wants to merge 1 commit intoopenwrt:masterfrom
ryjelsum wants to merge 1 commit intoopenwrt:masterfrom
Conversation
Contributor
|
Formalities need fix |
ryjelsum
changed the title
Author
|
I think that force-push should fix the commit message formality issues? Let me know if there's anything else I need to fix up. |
Contributor
|
You could bump also the PKG_RELEASE |
Sometime in Dec 2025, domoticz's package started to fail to build after a dependency update.The root of the problem is LTO, seemingly in combination with usage of -D_FORTIFY_SOURCE=1. LTO doesn't seem to be actively tested in domoticz's development anymore, so it is probably best to disable it. See openwrt#29004 Signed-off-by: Rudi Knauss <ryjelsum@gmail.com>
Contributor
|
Are you sure that just the LTO thing is the issue? I am seeing also some: This looks like boost compat failure? Mind taking a look at this patch? There may be something else missing. |
commodo
added a commit
to commodo/packages
that referenced
this pull request
May 2, 2026
boost::asio::post() without an explicit executor fails to compile with Boost >= 1.82 due to changes in the executor model: bare lambdas no longer have an implicit system executor that satisfies the blocking.never requirement. Pass io_context_ explicitly as the first argument so the handler is dispatched on the correct io_context thread, which is the original intent of the call (making stop() safe to call from any thread). Add test.sh domoticz is a daemon requiring a database and network port; it does not implement a --version flag. Verify the binary is present and executable. Disable LTO to fix link failure on i386 with musl fortify Suggested via openwrt#29239 Also tested. Signed-off-by: Alexandru Ardelean <alex@shruggie.ro>
4 tasks
commodo
added a commit
to commodo/packages
that referenced
this pull request
May 2, 2026
boost::asio::post() without an explicit executor fails to compile with Boost >= 1.82 due to changes in the executor model: bare lambdas no longer have an implicit system executor that satisfies the blocking.never requirement. Pass io_context_ explicitly as the first argument so the handler is dispatched on the correct io_context thread, which is the original intent of the call (making stop() safe to call from any thread). Add test.sh domoticz is a daemon requiring a database and network port; it does not implement a --version flag. Verify the binary is present and executable. Disable LTO to fix link failure on i386 with musl fortify Suggested via openwrt#29239 Also tested. Signed-off-by: Alexandru Ardelean <alex@shruggie.ro>
commodo
added a commit
to commodo/packages
that referenced
this pull request
May 2, 2026
boost::asio::post() without an explicit executor fails to compile with Boost >= 1.82 due to changes in the executor model: bare lambdas no longer have an implicit system executor that satisfies the blocking.never requirement. Pass io_context_ explicitly as the first argument so the handler is dispatched on the correct io_context thread, which is the original intent of the call (making stop() safe to call from any thread). Add test.sh domoticz is a daemon requiring a database and network port; it does not implement a --version flag. Verify the binary is present and executable. Disable LTO to fix link failure on i386 with musl fortify Suggested via openwrt#29239 Also tested. Signed-off-by: Alexandru Ardelean <alex@shruggie.ro>
GeorgeSapkin
pushed a commit
to commodo/packages
that referenced
this pull request
May 2, 2026
boost::asio::post() without an explicit executor fails to compile with Boost >= 1.82 due to changes in the executor model: bare lambdas no longer have an implicit system executor that satisfies the blocking.never requirement. Pass io_context_ explicitly as the first argument so the handler is dispatched on the correct io_context thread, which is the original intent of the call (making stop() safe to call from any thread). Add test.sh domoticz is a daemon requiring a database and network port; it does not implement a --version flag. Verify the binary is present and executable. Disable LTO to fix link failure on i386 with musl fortify Suggested via openwrt#29239 Also tested. Signed-off-by: Alexandru Ardelean <alex@shruggie.ro>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📦 Package Details
Maintainer: @dwmw2
Description:
Sometime in Dec 2025, domoticz's package started to fail to build after a dependency update. The root of the problem is LTO, seemingly in combination with usage of -D_FORTIFY_SOURCE=1. LTO doesn't seem to be actively tested in domoticz's development anymore, so it is probably best to disable it. (Unless someone else has a better suggestion!)
See #29004
🧪 Run Testing Details
(Compiled into an image and run on a device, and checked for basic functionality.)
✅ Formalities