From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master] xfont_font-util: convert to the autotools infrastructure
Date: Thu, 25 Feb 2010 08:44:22 +0100 [thread overview]
Message-ID: <20100225084422.63ef8c84@surf> (raw)
In-Reply-To: <4B85ACF0.4000005@carallon.com>
On Wed, 24 Feb 2010 22:49:20 +0000
Will Wagner <will_wagner@carallon.com> wrote:
> > Why do we need POST_INSTALL_STAGING hook when we installed only to
> > TARGET?
>
> I also have done a similar fix. I believe it is need in staging so
> that the pkgconfig info is correct, otherwise other things don't build
Ok. I've just sent a patch to fix this.
However, the way xfont_font-util is handled today is horrible. The
post-install script removes binaries compiled for the target from the
staging directory, and replaces them by symbolic links to binaries on
the host (making the incorrect assumption that they are available).
So, xfont_font-util needs be compiled for the host (using the new
infrastructure we have).
I haven't looked at the details, why are pkgconfig files needed for
font-utils ?
> I have also have patches to submit for X.Org 7.5, was just waiting
> for 2.10 release before submitting.
Great!
Could you cooperate with Paulius on this ? Like setting up a git tree
somewhere where you can collaborate and show us your code before
submitting it ?
Thanks !
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-02-25 7:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 20:27 [Buildroot] [git commit master] xfont_font-util: convert to the autotools infrastructure Thomas Petazzoni
2010-02-23 21:43 ` Paulius Zaleckas
2010-02-23 21:49 ` Peter Korsgaard
2010-02-24 20:19 ` Paulius Zaleckas
2010-02-24 20:46 ` Peter Korsgaard
2010-02-24 22:49 ` Will Wagner
2010-02-25 7:44 ` Thomas Petazzoni [this message]
2010-02-25 19:42 ` Paulius Zaleckas
2010-02-25 17:13 ` William Wagner
2010-02-25 19:08 ` Peter Korsgaard
2010-02-26 7:44 ` Thomas Petazzoni
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=20100225084422.63ef8c84@surf \
--to=thomas.petazzoni@free-electrons.com \
--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