Skip to contentSkip to conversation

New: Busybox static build fails due to missing libtirpc

Buildroot bugzilla at busybox.net 1 participant 2 messages May 10, 2019

lore
Share & tools
lore
#0 lore raw

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

Bug ID: 11856
Summary: Busybox static build fails due to missing libtirpc
Product: buildroot
Version: 2019.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: pmorici at dev295.com
CC: buildroot at uclibc.org
Target Milestone: ---

The busybox build fails if the CONFIG_STATIC option is selected in the busybox config. The failure is caused by a missing static library libtirpc.

The libtirpc package doesn't build a static version by default. The --enable-static option needs to be added to LIBTIRPC_CONF_OPTS in package/libtirpc/libtirpc.mk

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 11856] Busybox static build fails due to missing libtirpc

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

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #1 from Thomas Petazzoni <[email protected]> --- 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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.