From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8651] New: libMonoPosixHelper.so wrong link reference in buildroot image
Date: Thu, 04 Feb 2016 13:15:13 +0000 [thread overview]
Message-ID: <bug-8651-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8651
Bug ID: 8651
Summary: libMonoPosixHelper.so wrong link reference in
buildroot image
Product: buildroot
Version: 2015.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: Markus.Egle at Qiagen.com
CC: buildroot at uclibc.org
Target Milestone: ---
With the current buildroot 2015.11.1 (initially seen with 2015.05) configured
to use mono, the libMonoPosixHelper.so will be searched in the
/home/userX/buildroot/output/host/usr/lib/ path. This path and file may exist
on my building machine, but not on the target.
I have a working workaround with creating this folder and copy
libMonoPosixHelper.so from /usr/lib at startup in the ram disk.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-02-04 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 13:15 bugzilla at busybox.net [this message]
2016-02-04 13:17 ` [Buildroot] [Bug 8651] libMonoPosixHelper.so wrong link reference in buildroot image bugzilla at busybox.net
2016-02-04 13:32 ` bugzilla at busybox.net
2016-02-04 14:24 ` bugzilla at busybox.net
2016-02-04 14:32 ` Angelo Compagnucci
2016-02-04 16:05 ` Thomas Petazzoni
2016-02-05 14:42 ` bugzilla at busybox.net
2016-02-05 16:06 ` bugzilla at busybox.net
2016-02-05 16:08 ` bugzilla at busybox.net
2016-02-05 16:36 ` bugzilla at busybox.net
2016-02-14 21:55 ` bugzilla at busybox.net
2016-02-16 14:38 ` bugzilla at busybox.net
2016-02-21 9:36 ` bugzilla at busybox.net
2016-02-22 12:20 ` bugzilla at busybox.net
2016-02-22 12:27 ` bugzilla at busybox.net
2016-02-22 13:06 ` bugzilla at busybox.net
2016-02-25 23:35 ` 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-8651-163@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.