From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Eugene Tarassov <eugene@largest.net>,
Norbert Lange <nolange79@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/tcf-agent: fix uClibc-ng compile on ARM
Date: Mon, 14 Aug 2023 16:53:43 +0200 [thread overview]
Message-ID: <20230814165343.2e3936c6@windsurf> (raw)
In-Reply-To: <ZNiFAM4q72gwMume@waldemar-brodkorb.de>
On Sun, 13 Aug 2023 09:23:44 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> +ifeq ($(BR2_STATIC_LIBS),y)
> +ifeq ($(BR2_ARM_INSTRUCTIONS_THUMB),y)
> +TCF_AGENT_CONF_OPTS += -DCMAKE_C_FLAGS="$(TARGET_CFLAGS) -marm"
> +endif
> +endif
What is the situation with musl?
With glibc, BR2_STATIC_LIBS=y is impossible.
But with musl, BR2_STATIC_LIBS=y is possible. Is getauxval() always
supported on musl, regardless of static or shared?
Also, shouldn't the horrible "# define USE_getauxval
(defined(__GLIBC__) && (__GLIBC__ > 2 || (__GLIBC__ == 2 &&
__GLIBC_MINOR__ >= 16)) || (defined(__UCLIBC__) &&
defined(__HAVE_SHARED__)))" be turned into a proper CMake test ?
Thanks!
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
next prev parent reply other threads:[~2023-08-14 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 7:23 [Buildroot] [PATCH 2/2] package/tcf-agent: fix uClibc-ng compile on ARM Waldemar Brodkorb
2023-08-14 14:53 ` Thomas Petazzoni via buildroot [this message]
2023-08-15 3:36 ` Waldemar Brodkorb
2023-08-17 9:59 ` Thomas Petazzoni via buildroot
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=20230814165343.2e3936c6@windsurf \
--to=buildroot@buildroot.org \
--cc=eugene@largest.net \
--cc=nolange79@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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.