From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Michael 'Mickey' Lauer : ltrace: fix wrong path to coreutils-native and add actual dependency
Date: Sun, 15 Nov 2009 17:42:26 +0000 (UTC) [thread overview]
Message-ID: <hdpei2$9pm$1@ger.gmane.org> (raw)
In-Reply-To: E1N9c2H-0004ay-Ni@melo.openembedded.org
git version control wrote:
> Module: openembedded.git
> Branch: org.openembedded.dev
> Commit: 7df40b3378412f4700224e44042656159bc8f86c URL:
> http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=7df40b3378412f4700224e44042656159bc8f86c
>
> Author: Michael 'Mickey' Lauer
> <mickey@vanille-media.de> Date: Sun Nov 15
> 11:08:43 2009 +0100
>
> ltrace: fix wrong path to coreutils-native and add actual dependency
Hmmm. This broke ltrace for me (install.coreutils-native not found).
Do you have any pending patches on coreutils-native?
--
With best wishes
Dmitry
next parent reply other threads:[~2009-11-15 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1N9c2H-0004ay-Ni@melo.openembedded.org>
2009-11-15 17:42 ` Dmitry Eremin-Solenikov [this message]
2009-11-15 20:05 ` Michael 'Mickey' Lauer : ltrace: fix wrong path to coreutils-native and add actual dependency Michael Lauer
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='hdpei2$9pm$1@ger.gmane.org' \
--to=dbaryshkov@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.