All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Tollerton <rich.tollerton@ni.com>
To: yocto@yoctoproject.org, ajlennon@dynamicdevices.co.uk
Subject: [meta-mono] [RFC] [PATCH 0/1] Force MONO_CFG_DIR
Date: Fri, 17 Jul 2015 11:57:12 -0500	[thread overview]
Message-ID: <cover.1437151912.git.rich.tollerton@ni.com> (raw)

Hi Alex,

When you mentioned having weird build troubles, that reminded me that I
was seeing weird build problems of my own, that I had been refraining
from sending patches on until I could better characterize the issue.

If you've been seeing weird build failures in executables that really
should never be failing in the first place -- i.e., gacutils failures,
or "invalid resx file", or anything involving not being able to dlopen
libc or being unable to open /etc/mono/config -- you might be interested
in this patch.

That said, if you *don't* have problems compiling to an ARM sysroot, I'd
be interested in knowing that too. :F


The following changes since commit 041cc6b70c7fb3b55e73b90b1a101844da1726b2:

  README: Update to remove references to mono < 3.12.1 (2015-07-17 12:38:32 +0100)

are available in the git repository at:

  git://github.com/rtollert/meta-mono dev/rtollert/v5/mono-cfg
  https://github.com/rtollert/meta-mono/tree/dev/rtollert/v5/mono-cfg

Richard Tollerton (1):
  mono.bbclass: set MONO_CFG_DIR

 classes/mono.bbclass | 2 ++
 1 file changed, 2 insertions(+)

-- 
2.4.4



             reply	other threads:[~2015-07-17 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 16:57 Richard Tollerton [this message]
2015-07-17 16:57 ` [meta-mono] [RFC] [PATCH 1/1] mono.bbclass: set MONO_CFG_DIR Richard Tollerton
2015-07-17 17:26 ` [meta-mono] [RFC] [PATCH 0/1] Force MONO_CFG_DIR Alex J Lennon
2015-07-17 18:24   ` Richard Tollerton
2015-07-17 18:44     ` Alex J Lennon
2015-07-18  9:29       ` Alex J Lennon
2015-07-20 18:11         ` Richard Tollerton
2015-07-20 18:16           ` Alex J Lennon

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=cover.1437151912.git.rich.tollerton@ni.com \
    --to=rich.tollerton@ni.com \
    --cc=ajlennon@dynamicdevices.co.uk \
    --cc=yocto@yoctoproject.org \
    /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.