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:51:19 +0000 (UTC)	[thread overview]
Message-ID: <20140815105119.83FAF9D45F@busybox.osuosl.org> (raw)
In-Reply-To: <bug-7322-163@https.bugs.busybox.net/>

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

--- Comment #2 from Gustavo Zacarias <gustavo@zacarias.com.ar> 2014-08-15 10:51:19 UTC ---
There's already a config symbol for OpenMP (libgomp) support which could easily
be extended.
A quick fix for 2014.08 would be to --disable-openmp for imagemagick if
BR2_GCC_ENABLE_OPENMP isn't set (it's just used/supported for the internal
toolchain backend so nothing to worry about there, otherwise the test is
automatic).

Going forward i'd just copy it if it's available, it's not that big, an ARMv5
libgomp.so is roughly 100 KiB without stripping.
We could introduce a config knob like BR2_TOOLCHAIN_EXTERNAL_INET_RPC and those
but really, it's just complicating things i think.

-- 
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.

  parent reply	other threads:[~2014-08-15 10:51 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 ` [Buildroot] [Bug 7322] " bugzilla at busybox.net
2014-08-15 10:51 ` bugzilla at busybox.net [this message]
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=20140815105119.83FAF9D45F@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.