Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nelson <robert.nelson.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] What is the best way to deactivate XML Parser (expat) for ARM build?
Date: Thu, 01 May 2008 10:55:43 -0500	[thread overview]
Message-ID: <4819E7FF.5000902@gmail.com> (raw)
In-Reply-To: <326f33790805010751v24facd35o4207041c297da12c@mail.gmail.com>

-- added CC to Buildroot List

Hi Arun,

I've recently run into this too...  for some reason the expat dependency 
isn't properly built with the default at91sam9263_defconfig.  Until this 
gets fixed upstream, I've been issuing an "make expat" after the error 
first occurs, this moves the generated libexpat into the correct 
directory.. After which the build process will continue till the next 
error. (checking for GLIB - version >= 2.2.0... no)

Robert Nelson
FAE - Digi-Key

Arun Reddy wrote:
> I have been stuck for quite a few days on a problem dealing with the 
> build process failing because it cannot find the XML Parser library 
> libexpat. I was wondering is this even necessary for the build to 
> complete? Can I deactivate it? It seems my problem is very unique and 
> no other people have encountered it when doing an ARM build, so how 
> did you guys deactivate the XML Parser?
>
> Thank you.

  reply	other threads:[~2008-05-01 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 14:51 [Buildroot] What is the best way to deactivate XML Parser (expat) for ARM build? Arun Reddy
2008-05-01 15:55 ` Robert Nelson [this message]
2008-05-01 16:16   ` Arun Reddy
2008-05-01 17:14     ` Robert Nelson
2008-05-01 17:23       ` Arun Reddy

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=4819E7FF.5000902@gmail.com \
    --to=robert.nelson.work@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