From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10996] bogus musl ARM toolchain
Date: Sun, 13 May 2018 20:16:32 +0000 [thread overview]
Message-ID: <bug-10996-163-6ekbgvrVDY@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10996-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10996
--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
(In reply to Yann E. MORIN from comment #2)
Nope, because you're looking at the wrong place. The reason why the build fail
is because the "configuration" step which detects if mktime() is available or
not fails and concludes that mktime() is not available. See the string "
Check for mktime". Due to this, NO_MKTIME is defined, and this code path is
broken in util.c/timezone.c.
So there are really two problems:
(1) That is doesn't detect the availability of mktime() because -static is not
passed during the detection test.
(2) That the NO_MKTIME case is broken.
However, I believe (2) is not really relevant for Buildroot, as all three C
libraries provide mktime(). So all we need to fix is (1).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-05-13 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:41 [Buildroot] [Bug 10996] New: bogus musl ARM toolchain bugzilla at busybox.net
2018-05-11 15:53 ` [Buildroot] [Bug 10996] " bugzilla at busybox.net
2018-05-13 20:05 ` bugzilla at busybox.net
2018-05-13 20:16 ` bugzilla at busybox.net [this message]
2018-08-14 20:25 ` bugzilla at busybox.net
2018-08-14 22:31 ` bugzilla at busybox.net
2018-08-15 11:38 ` bugzilla at busybox.net
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=bug-10996-163-6ekbgvrVDY@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.