All of lore.kernel.org
 help / color / mirror / Atom feed
From: lancethepants <lancethepants@gmail.com>
To: buildroot@buildroot.org
Cc: lancethepants <lancethepants@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 1/1] package/musl-fts: always build static library
Date: Wed, 24 Aug 2022 14:26:17 -0600	[thread overview]
Message-ID: <20220824202617.21650-1-lancethepants@gmail.com> (raw)

musl-fts provides features left out of musl that are included in other libc's.

This patch always enables building the static library so
that it is always present with musl's libc.a when enabled.

For those that are using buildroot for toolchain creation
and want to static link, then libfts.a is available.

Signed-off-by: Lance Fredrickson <lancethepants@gmail.com>
Signed-off-by: lancethepants <lancethepants@gmail.com>
---
 package/musl-fts/musl-fts.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/musl-fts/musl-fts.mk b/package/musl-fts/musl-fts.mk
index dd7f1f9ea0..fcad9c3d75 100644
--- a/package/musl-fts/musl-fts.mk
+++ b/package/musl-fts/musl-fts.mk
@@ -12,5 +12,6 @@ MUSL_FTS_LICENSE_FILES = COPYING
 # pkg-config needed for autoreconf
 MUSL_FTS_DEPENDENCIES = host-pkgconf
 MUSL_FTS_INSTALL_STAGING = YES
+MUSL_FTS_CONF_OPTS += --enable-static
 
 $(eval $(autotools-package))
-- 
2.20.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-08-24 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 20:26 lancethepants [this message]
2022-08-27 13:38 ` [Buildroot] [PATCH 1/1] package/musl-fts: always build static library Yann E. MORIN
2022-08-29 14:52   ` Lance Fredrickson
2022-08-29 15:17     ` Yann E. MORIN

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=20220824202617.21650-1-lancethepants@gmail.com \
    --to=lancethepants@gmail.com \
    --cc=buildroot@buildroot.org \
    --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 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.