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 7322] libgomp dependency issue with imagemagick
Date: Fri, 15 Aug 2014 10:35:55 +0000 (UTC)	[thread overview]
Message-ID: <20140815103555.9AF9A9D45F@busybox.osuosl.org> (raw)
In-Reply-To: <bug-7322-163@https.bugs.busybox.net/>

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

--- Comment #1 from Thomas De Schampheleire <patrickdepinguin@gmail.com> 2014-08-15 10:35:54 UTC ---
Thanks for your clear bug report.
How 'standard' is libgomp in external toolchains? Is it something that is
present in a typical toolchain, or does it have to be enabled explicitly?

How large is this library (stripped)?

We could simply copy libgomp* to the target when present, regardless of any
package dependency like imagemagick.
In toolchain/toolchain-external/toolchain-external.mk, we would have to extend
the LIB_EXTERNAL_LIBS variable with libgomp.

If either the presence of libgomp is not standard, or it is sufficiently small,
then this would be a fine strategy I believe...

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  reply	other threads:[~2014-08-15 10:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 21:36 [Buildroot] [Bug 7322] New: libgomp dependency issue with imagemagick bugzilla at busybox.net
2014-08-15 10:35 ` bugzilla at busybox.net [this message]
2014-08-15 10:51 ` [Buildroot] [Bug 7322] " bugzilla at busybox.net
2014-08-15 13:04 ` bugzilla at busybox.net
2014-08-15 13:52 ` bugzilla at busybox.net
2014-08-20 17:07 ` bugzilla at busybox.net
2014-08-21 20:21 ` 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=20140815103555.9AF9A9D45F@busybox.osuosl.org \
    --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.