From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1399] xfont_font-adobe-100dpi does not build
Date: Mon, 12 Apr 2010 14:19:32 +0000 (UTC) [thread overview]
Message-ID: <20100412141932.CEEB18DBDA@busybox.osuosl.org> (raw)
In-Reply-To: <bug-1399-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=1399
--- Comment #7 from Paulius Zaleckas <paulius.zaleckas@gmail.com> 2010-04-12 14:19:32 UTC ---
(In reply to comment #6)
> I checked for bdftopcf on the host and it is there even without fontutils
> installed.
>
How you checked for it?
It should output usage documentation if you just type "bdftopcf -" in terminal.
And if it really is present on your host I have no idea why buildroot fails to
compile fonts...
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2010-04-12 14:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 6:42 [Buildroot] [Bug 1399] New: xfont_font-adobe-100dpi does not build bugzilla at busybox.net
2010-03-26 8:42 ` [Buildroot] [Bug 1399] " bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-04-11 14:58 ` bugzilla at busybox.net
2010-04-11 22:07 ` bugzilla at busybox.net
2010-04-11 22:14 ` bugzilla at busybox.net
2010-04-11 22:16 ` bugzilla at busybox.net
2010-04-11 22:40 ` bugzilla at busybox.net
2010-04-12 9:35 ` bugzilla at busybox.net
2010-04-12 14:19 ` bugzilla at busybox.net [this message]
2010-04-12 14:58 ` bugzilla at busybox.net
2010-04-12 21:31 ` bugzilla at busybox.net
2010-05-08 8:29 ` bugzilla at busybox.net
2010-05-08 11:01 ` bugzilla at busybox.net
2010-05-08 11:48 ` bugzilla at busybox.net
2010-05-09 6:38 ` bugzilla at busybox.net
2010-06-24 10:28 ` bugzilla at busybox.net
2010-06-25 9:36 ` bugzilla at busybox.net
2010-06-25 10:29 ` bugzilla at busybox.net
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=20100412141932.CEEB18DBDA@busybox.osuosl.org \
--to=bugzilla@busybox.net \
--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