From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] xfce_session_4.6.{1, 2}: explicitly pass the path of `iceauth`
Date: Wed, 23 Mar 2011 08:14:22 +0100 [thread overview]
Message-ID: <imc6ke$j7j$1@dough.gmane.org> (raw)
In-Reply-To: <201103230133.06164.schnitzeltony@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-03-11 01:33, Andreas Mueller wrote:
> Anyway: In 'xfce4-session' / config.log I found:
>
> | configure:15972: checking for iceauth
> | configure:15990: found */usr/bin/iceauth*
> | configure:16002: result: /usr/bin/iceauth
>
> So - as Khem suggested - and with xfce4-session: RDEPENDS_${PN}="iceauth" I:
> - changed iceauth to extent to iceauth-native.
> - changed xfce4-session: DEPENDS = "iceauth-native ..."
No, it only wants to probe for the PATH of the binary to encode into the
result. We do NOT want target binaries to point to your builddir instead
of ${bindir}.
As I said before, Pauls patch does the right thing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNiZ3OMkyGM64RGpERAhGkAJ9DcOr2vrAnAEkR8YmsNYSIJokHeACeLMiv
s5rQTqwrhSBj+oyZCHdRM6w=
=Fjad
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-23 7:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:34 xfce4-session: task configure fails with `checking for iceauth... no` Paul Menzel
2011-03-15 16:06 ` Paul Menzel
2011-03-15 16:24 ` Khem Raj
2011-03-17 12:28 ` Paul Menzel
2011-03-17 22:46 ` Paul Menzel
2011-03-17 22:56 ` Khem Raj
2011-03-18 12:00 ` [PATCH] xfce_session_4.6.{1, 2}: explicitly pass the path of `iceauth` Paul Menzel
2011-03-19 18:33 ` Khem Raj
2011-03-20 1:10 ` Paul Menzel
2011-03-20 4:32 ` Khem Raj
2011-03-20 10:16 ` Paul Menzel
2011-03-20 18:01 ` Khem Raj
2011-03-20 21:05 ` Paul Menzel
2011-03-20 13:03 ` Koen Kooi
2011-03-23 0:33 ` Andreas Mueller
2011-03-23 0:51 ` Paul Menzel
2011-03-23 7:14 ` Koen Kooi [this message]
2011-03-23 8:35 ` Andreas Mueller
2011-03-23 9:51 ` Paul Menzel
2011-03-23 10:19 ` Andreas Mueller
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='imc6ke$j7j$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.