Replies: 5 comments 12 replies
-
It seems that the macro is undefined for older gcc versions.
or to provide a fallback
|
Beta Was this translation helpful? Give feedback.
-
I also experienced this when the change was introduced, but I could not always reproduce it, so I did only mention it in a coment: #1037 (reply in thread) @fda77, seems that the changes 407b953 and e389075 cause some trouble and are not the correct way to solve the issue #1037? Regards! |
Beta Was this translation helpful? Give feedback.
-
On Tue, 17 Sep 2024 02:55:53 -0700, Peter Fichtner ***@***.***> wrote:
> Es hat wohl nichts mit den compiler zu tun sondern der verwendeten
> libc
Identische Config mit Änderung des Hardware Typs von 7570 auf 7490
baut erfolgreich was ein Indiz ist, dass es nicht vom Host Compiler
abhängt
I also had issues once but not in repeated build tries for the _same_
hardware.
So it might also be another issue.
@fda77: Could this be what @MasterRoCcO means with "test yourself"?
Regards!
|
Beta Was this translation helpful? Give feedback.
-
On Tue, 17 Sep 2024 06:47:46 -0700, fda77 ***@***.***> wrote:
einigt euch einfach auf eine der möglichen lösungen
I am not a developer. I think the maintainers who have write access
should decide how to fix issues.
|
Beta Was this translation helpful? Give feedback.
-
Changeset between last successful build and error is (without juis/docs automatic updates)
d9d8a90 mosquitto: fixed the binary path of mosquitto_passwd since it changed with mosquitto 2.x
e389075 gcc 3.4: gcc14 compatibility, thx @dreirund - refs #1037
407b953 binutils: gcc14 compiatibility - refs #1037
ab347d7 bump python3-host
... so I suspect the error was caused by 407b953 and/or e389075
All the log message:
Beta Was this translation helpful? Give feedback.
All reactions