From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libgtk2
Date: Thu, 15 Jan 2009 09:36:21 +0100 [thread overview]
Message-ID: <20090115083621.GA15748@zelow.no> (raw)
In-Reply-To: <20090114221114.73CB776C8E@busybox.osuosl.org>
On Wed, Jan 14, 2009 at 10:11:14PM +0000, ulf at uclibc.org wrote:
>
> Log:
> Force use of HOST_GLIB instead of /usr/bin for libgtk2
>
> Modified:
> trunk/buildroot/package/libgtk2/libgtk2.mk
I'll repeat myself, please answer.
Any reason we do this instead of using good old PATH?
Using PATH and having STAGING_DIR/BIN first in it will give the user an option
to choose wether he wants to use the host provided or his own.
So what is wrong with PATH and makes this hack a necessity?
Thomas.
next prev parent reply other threads:[~2009-01-15 8:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 22:11 [Buildroot] svn commit: trunk/buildroot/package/libgtk2 ulf at uclibc.org
2009-01-15 8:36 ` Thomas Lundquist [this message]
2009-01-15 20:18 ` Ulf Samuelsson
2009-01-15 20:26 ` Peter Korsgaard
2009-01-15 20:37 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2009-01-18 10:57 ulf at uclibc.org
2009-01-18 11:05 ` Peter Korsgaard
2009-01-18 13:11 ` Sven Neumann
2009-01-18 13:43 ` Daniel Laird
2009-01-18 13:48 ` Peter Korsgaard
2008-12-31 9:35 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-10-27 9:45 jacmet at uclibc.org
2008-10-18 7:00 jacmet at uclibc.org
2008-08-26 13:45 laird at uclibc.org
2008-08-26 12:19 laird at uclibc.org
2008-08-26 13:15 ` Peter Korsgaard
2008-08-26 13:32 ` Daniel Laird
2008-08-26 13:38 ` Peter Korsgaard
2008-08-26 14:04 ` Bernhard Reutner-Fischer
2008-08-26 14:07 ` Bernhard Reutner-Fischer
2008-08-26 14:54 ` Peter Korsgaard
2008-08-26 13:48 ` Bernhard Reutner-Fischer
2008-08-26 14:07 ` Peter Korsgaard
2008-08-26 14:11 ` Bernhard Reutner-Fischer
2008-08-26 14:13 ` Daniel Laird
2008-08-26 13:42 ` Ormund Williams
2008-08-26 13:49 ` Daniel Laird
2008-07-08 10:09 ulf at uclibc.org
2008-07-07 11:09 ulf at uclibc.org
2008-07-06 6:25 ulf at uclibc.org
2007-02-01 19:20 andersen at uclibc.org
2007-01-17 11:27 jacmet at uclibc.org
2007-01-17 0:04 andersen at uclibc.org
2007-01-14 23:27 andersen at uclibc.org
2007-01-14 23:26 andersen at uclibc.org
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=20090115083621.GA15748@zelow.no \
--to=lists@zelow.no \
--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