Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] unable to build fontconfig
Date: Wed, 19 Sep 2007 23:37:29 +0200	[thread overview]
Message-ID: <20070919213729.GW20058@aon.at> (raw)
In-Reply-To: <1190148550.4516.0.camel@aeglos.sweden.atmel.com>

On Tue, Sep 18, 2007 at 10:49:10PM +0200, Ulf Samuelsson wrote:
>tis 2007-09-18 klockan 11:25 -0700 skrev Kay McCormick:
>> Sorry, there is a chain of dependencies, but I want to use X.  Does X work at this time?
>> Is there a way to use X without fontconfig
>> 
>
>
>I have failed building all three versions.

I have this patch lying around:
uclibc.org/~aldot/buildroot/package_fontconfig_host-tools.patch
it's ment to be put into package/fonctconfig/host-tools.patch
and needs a patch ontop of that that does an autoreconf.
I don't need fontconfig and will not finish the patch above, so do
whatever you want.

Perhaps that gets you started (i don't remember if that fixed fontconfig
for me as a whole or if it was just one part of the mess). But remember
that ultimatively, fontconfig should be fixed upstream..
>
>> You cannot disable FONTCONFIG because something
>> has "selected" this package.
>> If you, in menuconfig, look at the help item
>> for fontconfig, it will tell you what forces
>> fontconfig to be built.
>> Possibly there is a chain of dependencies.

      reply	other threads:[~2007-09-19 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 23:55 [Buildroot] unable to build fontconfig Kay McCormick
2007-09-18  6:35 ` Ulf Samuelsson
2007-09-18 18:25   ` Kay McCormick
2007-09-18 20:49     ` Ulf Samuelsson
2007-09-19 21:37       ` Bernhard Fischer [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=20070919213729.GW20058@aon.at \
    --to=rep.dot.nop@gmail.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