Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter.korsgaard@barco.com>
To: buildroot@busybox.net
Subject: [Buildroot] __ctype_b undefined reference after adding fontconfig support
Date: Wed, 23 May 2007 08:56:40 +0200	[thread overview]
Message-ID: <87d50st4d3.fsf@sleipner.barco.com> (raw)
In-Reply-To: <015f01c798b4$ac3fdc30$2600a8c0@engineering5> (Christopher Reder's message of "Thu, 17 May 2007 13:53:35 -0500")

>>>>> "CR" == Christopher Reder <creder@digitalcpt.com> writes:

Hi,

CR> In wanting to use Matchbox as added by Assen, I enabled those
CR> packages which require fontconfig and freetype.  In doing so, I
CR> received the following error which I found as reported a couple of
CR> weeks ago.  I am wondering if anyone else has encountered this and
CR> how to address it.  If there is a version of buildroot that I can
CR> go back to, then I'd be happy to do it.  I have binutils 2.17,
CR> uclibc 0.9.29 and gcc 4.1.2 selected as the toolchain for
CR> buildroot.

fontconfig should be fixed now. Could you give it a try?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2007-05-23  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 10:21 [Buildroot] x11r7-matchbox-tslib patch Assen Stoyanov
2007-05-17 18:53 ` [Buildroot] __ctype_b undefined reference after adding fontconfig support Christopher Reder
2007-05-23  6:56   ` Peter Korsgaard [this message]
2007-05-28 14:21     ` christophe Dion
2007-05-28 16:37       ` rafael2k
2007-05-24 16:49 ` [Buildroot] x11r7-matchbox-tslib patch Christopher Reder
  -- strict thread matches above, loose matches on Subject: below --
2007-05-17 19:05 [Buildroot] __ctype_b undefined reference after adding fontconfig support Christopher Reder
2007-05-21  9:52 christophe Dion

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=87d50st4d3.fsf@sleipner.barco.com \
    --to=peter.korsgaard@barco.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