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

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

--- Comment #3 from Beno?t Th?baudeau <benoit.thebaudeau.dev@gmail.com> 2014-08-15 13:04:47 UTC ---
Yes, libgomp is not very big. It seems to be now present in most toolchains,
but it is optional.

I also think that doing something for imagemagick here is the wrong way to go,
not only because it complicates things, but also because other packages may
silently (unless they're run on the target) be affected by the same issue,
either for libgomp or for another toolchain library.

I agree that something like BR2_TOOLCHAIN_EXTERNAL_INET_RPC would be overkill,
because this is rather used for feature / package filtering than for library
installation.

Looking at copy_toolchain_lib_root, adding libgomp.so* to LIB_EXTERNAL_LIBS
should work even if this library is not available, so this is indeed a good
solution. And this will make it possible to easily add other optional standard
(i.e. non-exotic) libraries in the same way in the future if a similar issue
happens elsewhere.

I will probably send a patch next week if nobody beats me at it.

-- 
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 13:04 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
2014-08-15 13:04 ` bugzilla at busybox.net [this message]
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=20140815130448.9D4949D463@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.