From: Michael J. Hammel <buildroot@graphics-muse.org>
To: buildroot@busybox.net
Subject: [Buildroot] xfonts error in 2011.02
Date: Sun, 10 Apr 2011 09:38:28 -0600 [thread overview]
Message-ID: <1302449908.6468.3.camel@kepler.graphics-muse.org> (raw)
In-Reply-To: <1302385414.7244.23.camel@galileo.graphics-muse.org>
On Sat, 2011-04-09 at 15:43 -0600, Michael J. Hammel wrote:
> This seems related to this patch:
> http://git.buildroot.net/buildroot/commit/?id=117a8ea0eaabec72d7637f80f7a55fbba9ce67bf
>
> I've applied the patch but it doesn't appear to fix the problem. Also,
> is this patch correct? It seems the following:
>
> ++ if (pcsysrootdir &&
> ++ (!strcmp(variable_name, "includedir") ||
> ++ !strcmp(variable_name, "libdir")))
After more testing it appears this is probably correct, but is missing
one additional variable: mapdir. When I added mapdir to the patch the
build appears to complete successfully and the fonts are in the correct
location.
I don't know if this is the correct solution, but it works. So I'll
post a bug report for it in a little while.
--
Michael J. Hammel <buildroot@graphics-muse.org>
prev parent reply other threads:[~2011-04-10 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 21:43 [Buildroot] xfonts error in 2011.02 Michael J. Hammel
2011-04-10 15:38 ` Michael J. Hammel [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=1302449908.6468.3.camel@kepler.graphics-muse.org \
--to=buildroot@graphics-muse.org \
--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