From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] libgomp.so.1.0.0 not in target image
Date: Wed, 14 Nov 2012 00:06:34 +0100 [thread overview]
Message-ID: <50A2D27A.5000706@mind.be> (raw)
In-Reply-To: <20121113231021.6995bd28@skate>
On 13/11/12 23:10, Thomas Petazzoni wrote:
> Arnout,
>
> On Tue, 13 Nov 2012 18:34:32 +0100, Arnout Vandecappelle wrote:
>
>> Thomas, I think this should be fixed by adding libgomp to
>> LIB_EXTERNAL_LIBS in ext-tool.mk. Is that right? Will that also
>> work if libgomp doesn't exist?
>
> Do we really need to be linked against libgomp? Under what conditions
> does that happen? Can't we avoid that even if the toolchain has OpenMP
> support?
beecrypt links agains libgomp if libgomp is available; rpm uses beecrypt.
The point is not avoiding to link with libgomp (you have to do that explicitly),
the point is that if somebody links against libgomp, it has to be in target.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-13 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 15:30 [Buildroot] libgomp.so.1.0.0 not in target image Alexander Khryukin
2012-11-13 17:34 ` Arnout Vandecappelle
2012-11-13 20:55 ` Alexander Khryukin
2012-11-13 21:09 ` Arnout Vandecappelle
2012-11-13 21:19 ` Yann E. MORIN
2012-11-13 21:21 ` Arnout Vandecappelle
2012-11-13 21:31 ` Yann E. MORIN
2012-11-13 21:24 ` Alexander Khryukin
2012-11-13 22:10 ` Thomas Petazzoni
2012-11-13 23:06 ` Arnout Vandecappelle [this message]
2012-11-14 8:21 ` Thomas Petazzoni
2012-11-14 9:50 ` Alexander Khryukin
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=50A2D27A.5000706@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox