From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/memcached: fix uclibc-ng build
Date: Sat, 4 Nov 2023 22:30:22 +0100 [thread overview]
Message-ID: <20231104223022.5741ef0e@windsurf> (raw)
In-Reply-To: <20231001130459.840149-1-fontaine.fabrice@gmail.com>
On Sun, 1 Oct 2023 15:04:59 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following uclibc-ng build failure raised since bump to version
> 1.6.21 in commit 6ce55ab0ed3b7125cd11ecfe8c18aaf156b5f060 and
> https://github.com/memcached/memcached/commit/875371a75cbf1f92350de2d1fa0fae4a35ed572b:
>
> /home/buildroot/autobuild/instance-2/output-1/host/lib/gcc/arc-buildroot-linux-uclibc/10.2.0/../../../../arc-buildroot-linux-uclibc/bin/ld: memcached-thread.o: in function `thread_setname':
> thread.c:(.text+0xea2): undefined reference to `pthread_setname_np'
>
> Fixes:
> - http://autobuild.buildroot.org/results/e856d381f5ec7d2727f21c8bd46dacb456984416
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Thanks, applied!
> +Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> +Upstream: unsent yet (waiting feedback on first patch)
I think you should submit without waiting for feedback on your first
patch, it's a separate topic/issue.
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:[~2023-11-04 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 13:04 [Buildroot] [PATCH 1/1] package/memcached: fix uclibc-ng build Fabrice Fontaine
2023-11-04 21:30 ` 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=20231104223022.5741ef0e@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--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