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 10326] mesa3d package fails to build when BR2_SHARED_STATIC_LIBS=y
Date: Wed, 27 Sep 2017 19:07:20 +0000	[thread overview]
Message-ID: <bug-10326-163-De5fKxubAy@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10326-163@https.bugs.busybox.net/>

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

--- Comment #5 from Arnout Vandecappelle <arnout@mind.be> ---
I agree with Frederic, there is no reason to exclude mesa3d, since it builds
fine under SHARED_STATIC with the additional --disable-static option.
SHARED_STATIC is meant for building a shared-library based rootfs and still
allowing some (custom?) packages to link statically. So if some package is
shared-only (or static-only, for that matter), it should still be possible to
build it.

Frederic, would you send your proposal as a properly formatted patch to the
mailing list?
https://buildroot.org/downloads/manual/manual.html#submitting-patches

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

  parent reply	other threads:[~2017-09-27 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 12:49 [Buildroot] [Bug 10326] New: mesa3d package fails to build when BR2_SHARED_STATIC_LIBS=y bugzilla at busybox.net
2017-09-25 18:53 ` [Buildroot] [Bug 10326] " bugzilla at busybox.net
2017-09-26  7:06 ` bugzilla at busybox.net
2017-09-26 16:19 ` bugzilla at busybox.net
2017-09-27  8:13 ` bugzilla at busybox.net
2017-09-27 19:07 ` bugzilla at busybox.net [this message]
2017-11-11 22:40 ` bugzilla at busybox.net

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-10326-163-De5fKxubAy@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.