[Buildroot] unable to build fontconfig

[Buildroot] unable to build fontconfig

[Kay McCormick]

I can't disable fontconfig, but it won't build either!

 

autoreconf2.50: Entering directory `.'

autoreconf2.50: configure.in: not using Gettext

autoreconf2.50: running: aclocal -I
/home/kaym/src2/buildroot/build_i386/staging_dir/usr/share/aclocal
--force

aclocal:configure.in:64: warning: macro `AM_PROG_LIBTOOL' not found in
library

autoreconf2.50: configure.in: tracing

autoreconf2.50: configure.in: not using Libtool

autoreconf2.50: running: /usr/bin/autoconf
--include=/home/kaym/src2/buildroot/build_i386/staging_dir/usr/share/acl
ocal --force

configure.in:63: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL

      If this token and others are legitimate, please use
m4_pattern_allow.

      See the Autoconf documentation.

configure.in:64: error: possibly undefined macro: AM_PROG_LIBTOOL

autoreconf2.50: /usr/bin/autoconf failed with exit status: 1

make: ***
[/home/kaym/src2/buildroot/build_i386/fontconfig-2.4.2/.configured]
Error 1

 

Help!

 

Kay

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070917/888c102b/attachment-0001.htm 

[Buildroot] unable to build fontconfig

[Ulf Samuelsson]

m?n 2007-09-17 klockan 16:55 -0700 skrev Kay McCormick:
> I can?t disable fontconfig, but it won?t build either!
> 
>  
> 
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.

BR
Ulf Samuelsson

>  
> 
> Help!
> 
>  
> 
> Kay
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

[Buildroot] unable to build fontconfig

[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

-----Original Message-----
From: Ulf Samuelsson [mailto:ulf at atmel.com] 
Sent: Monday, September 17, 2007 11:36 PM
To: Kay McCormick
Cc: buildroot at uclibc.org
Subject: Re: [Buildroot] unable to build fontconfig

m?n 2007-09-17 klockan 16:55 -0700 skrev Kay McCormick:
> I can?t disable fontconfig, but it won?t build either!
> 
>  
> 
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.

BR
Ulf Samuelsson

>  
> 
> Help!
> 
>  
> 
> Kay
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

[Buildroot] unable to build fontconfig

[Ulf Samuelsson]

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.

> 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.
> 
> BR
> Ulf Samuelsson

-- 
Best Regards,
Ulf Samuelsson

[Buildroot] unable to build fontconfig

[Bernhard Fischer]

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.