Skip to contentSkip to conversation

New: thermald-1.9.1 compilation failure with musl 1.2.1

Buildroot bugzilla at busybox.net 1 participant 3 messages Nov 23, 2020

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=13336

Bug ID: 13336
Summary: thermald-1.9.1 compilation failure with musl 1.2.1
Product: buildroot
Version: 2020.08.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: mscdex at mscdex.net
CC: buildroot at uclibc.org
Target Milestone: ---

Created attachment 8681
--> https://bugs.busybox.net/attachment.cgi?id=8681&action=edit
Fix for musl 1.2.x

Host machine: Ubuntu 18.04
Buildroot version: 2020.08.2
Target: i586-buildroot-linux-musl-gcc (GCC 10.2.0)

Trying to build thermald 1.9.1 fails when compiling with musl 1.2.0+. The reason for this appears to be that musl now uses a 64-bit time_t on all architectures.

I've attached a patch I found from Yocto that fixes this issue.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 13336] thermald-1.9.1 compilation failure with musl 1.2.1

https://bugs.busybox.net/show_bug.cgi?id=13336

--- Comment #1 from Peter Seiderer <[email protected]> ---
Thanks for the bug report, see [1] for suggested buildroot patch/fix (using the upstream commit instead of the yocto patch)...

[1]
https://patchwork.ozlabs.org/project/buildroot/patch/20201123211248.23828-1-ps.report at gmx.net/

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#2 lore raw

[Buildroot] [Bug 13336] thermald-1.9.1 compilation failure with musl 1.2.1

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=13336

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Peter Korsgaard <[email protected]> --- Fixed in git master by Peter's patch

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.