From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@paral.in>
Cc: Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-06-02
Date: Fri, 3 Jun 2022 10:02:48 +0200 [thread overview]
Message-ID: <20220603100248.01f89db7@windsurf> (raw)
In-Reply-To: <CA+h8R2rTCXB1bu4_0Pwxx7yzkYrY9P8DTbkSTuKM8bEa50dJVA@mail.gmail.com>
Hello,
On Thu, 2 Jun 2022 21:48:56 -0700
Christian Stewart <christian@paral.in> wrote:
> Thomas,
>
> On Thu, Jun 2, 2022 at 9:44 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> > aarch64 | host-go-1.18.2 | http://autobuild.buildroot.net/results/24c9186f5583e2849fa1753f3bc3cfb1441c5a4e
>
> Building with musl on aarch64, pthread not defined errors,
>
> is BR2_TOOLCHAIN_HAS_THREADS set with musl, and if so, is pthread
> available there?
Well, there are several symbols causing problem which are not related
to pthread:
runtime/cgo(.text): relocation target stderr not defined
runtime/cgo(.text): relocation target fwrite not defined
runtime/cgo(.text): relocation target vfprintf not defined
runtime/cgo(.text): relocation target fputc not defined
runtime/cgo(.text): relocation target abort not defined
so I'm not sure the issue is pthread related here. Obviously musl does
implement fwrite, fputc, etc.
And yes, musl implements pthread, so BR2_TOOLCHAIN_HAS_THREADS is true
for musl-based configurations.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-06-03 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62999194.1c69fb81.b5e75.5008SMTPIN_ADDED_MISSING@mx.google.com>
2022-06-03 4:48 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-06-02 Christian Stewart via buildroot
2022-06-03 8:02 ` Thomas Petazzoni via buildroot [this message]
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=20220603100248.01f89db7@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@paral.in \
--cc=thomas.petazzoni@bootlin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox