All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11856] Busybox static build fails due to missing libtirpc
Date: Fri, 10 May 2019 07:29:22 +0000	[thread overview]
Message-ID: <bug-11856-163-qB9DOZ8lat@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11856-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11856

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
This is not a bug. By default Buildroot has the option BR2_SHARED_LIBS=y, which
means "build only shared libraries, link everything dynamically".

If you set BR2_STATIC_LIBS=y instead, then only static libraries will be built,
and everything will be statically linked.

If you set BR2_SHARED_STATIC_LIBS=y, then both static and shared libraries will
be built (when possible: some sub-par build systems only allow building either
static or shared libs, not both), and programs will generally be linked
dynamically, unless their build system explicitly links statically.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2019-05-10  7:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10  3:59 [Buildroot] [Bug 11856] New: Busybox static build fails due to missing libtirpc bugzilla at busybox.net
2019-05-10  7:29 ` bugzilla at busybox.net [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=bug-11856-163-qB9DOZ8lat@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.