From: Martin Ertsaas <martiert@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/5] sanity: Make the required utilities more platform specific.
Date: Tue, 15 Jan 2013 10:07:09 +0100 [thread overview]
Message-ID: <50F51C3D.1070904@gmail.com> (raw)
In-Reply-To: <1358237694.23113.17.camel@ted>
On 01/15/13 09:14, Richard Purdie wrote:
> which will then simplify the other part of the patch (make it
> unnecessary).
That is true, will make it a lot simpler.
What I know is still missing:
1) There are some errors with the paths, seems like stuff is not
correctly transfered to the sysroot, this is next on the agenda.
2) Make a class that does what chrpath does, but for install_name_tool,
going to do this as soon as I get an error on it.
3) Probably some errors after I get past the error I have now.
I agree that we should not merge a ton of these patches.
For my part, I can keep these in my repository until I have stuff
working. When we can compile everything I can do a pull request. If
someone wants to help, they can just pull from me and work against that
repo.
- Martin
prev parent reply other threads:[~2013-01-15 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 8:50 [PATCH 1/5] sanity: Make the required utilities more platform specific Martin Ertsaas
2013-01-10 8:50 ` [PATCH 2/5] quilt: Remove non-gnu.patch, and added configure flags for darwin Martin Ertsaas
2013-01-10 8:50 ` [PATCH 3/5] quilt: Don't use BUILD_ROOT on darwin Martin Ertsaas
2013-01-10 8:50 ` [PATCH 4/5] lib/oe/path.py: Use shutil.rmtree if the path we wish to remove is a directory Martin Ertsaas
2013-01-10 14:15 ` Chris Larson
2013-01-11 6:27 ` Martin Ertsaas
2013-01-11 14:55 ` Chris Larson
2013-01-10 8:50 ` [PATCH 5/5] sstate: Do not add the --no-run-if-empty arguement to xargs when on Darwin, as it is not supported Martin Ertsaas
2013-01-15 8:14 ` [PATCH 1/5] sanity: Make the required utilities more platform specific Richard Purdie
2013-01-15 9:07 ` Martin Ertsaas [this message]
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=50F51C3D.1070904@gmail.com \
--to=martiert@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.