From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8651] libMonoPosixHelper.so wrong link reference in buildroot image
Date: Thu, 4 Feb 2016 17:05:21 +0100 [thread overview]
Message-ID: <20160204170521.17c7d347@free-electrons.com> (raw)
In-Reply-To: <CA+TH9VmoyAYz+GG+6e+cMj3CzOgJQU9V0aYrUxKrRFz=kkPhNA@mail.gmail.com>
Dear Angelo Compagnucci,
On Thu, 4 Feb 2016 15:32:21 +0100, Angelo Compagnucci wrote:
> Dear Markus Egle,
>
> Could you try to have a look at file /etc/mono/config in your generated image?
You should reply in the bug tracker. I am not sure Markus is a
subscriber of the Buildroot mailing list, and I'm not sure sending
e-mails to bugzilla at busybox.net works.
Otherwise, thanks a lot for taking care of this Mono bug report. It is
good to see additional users testing this functionality, as it will
test it in different conditions.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-04 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 13:15 [Buildroot] [Bug 8651] New: libMonoPosixHelper.so wrong link reference in buildroot image bugzilla at busybox.net
2016-02-04 13:17 ` [Buildroot] [Bug 8651] " 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 [this message]
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=20160204170521.17c7d347@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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