All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] some tips for x11r7
Date: Mon, 24 Sep 2007 20:31:00 +0300	[thread overview]
Message-ID: <46F7F454.9060603@promwad.com> (raw)
In-Reply-To: <46F7CBF7.8040103@apexar.com.ar>

>>   
> Hi Ivan,
> 
> I was trying to solve the same problem as you: make X working in ARM, 
> but i'm getting this error when compiling FontConfig (the X server i 
> choose was x11r7):
> 
> 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
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> make: *** 
> [/home/dfons/buildroot_19987/build_arm/fontconfig-2.4.2/.configured] Error 1
> 
> Did you get this error? What can i do to solve it?
> 
> Regards,
> Diego A. Fons.

Hello,

No, do not have such an error. But I have fontconfig and fontconfig-devel rpms installed on my host PC -
may be this could be a reason why I do not see such errors. Are you using latest buildroot svn revision?

Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

  parent reply	other threads:[~2007-09-24 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23 19:16 [Buildroot] some tips for x11r7 Ivan Kuten
     [not found] ` <46F7CBF7.8040103@apexar.com.ar>
2007-09-24 17:31   ` Ivan Kuten [this message]
     [not found]     ` <46F8FB49.8050808@apexar.com.ar>
2007-09-26 12:15       ` Kuten Ivan

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=46F7F454.9060603@promwad.com \
    --to=ivan.kuten@promwad.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.