Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brad House <brad@mainstreetsoftworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] libxml2 fixes
Date: Tue, 07 Aug 2007 08:08:21 -0400	[thread overview]
Message-ID: <46B860B5.8050205@mainstreetsoftworks.com> (raw)
In-Reply-To: <12028348.post@talk.nabble.com>

>      After i applied ur patch, i am getting an error when compilling libxml2
> as missing xml-config file
> 
> <snip>
> <snip>

> /home/guru/project/original/toolchains/buildroot/build_arm/staging_dir/usr/bin/xml2-config:
> No such file or directory
> make: ***
> [/home/guru/project/original/toolchains/buildroot/build_arm/libxml2-2.6.29/libxml2.la]
> Error 
> 
>    But i see that xml-config is in my buildroot/build_arm/libxml2-2.6.29
> directory. i think its not copied to build_arm/staging_dir/usr/bin/. kindly
> let me know if i can manually copy the same or i should add/make  any
> changes.

Well, the 'make install' inside the libxml2.mk is responsible for
copying over the xml2-config to your staging_dir's usr/bin directory.

Can you run:
make libxml2-clean
rm -rf build_arm/libxml2-2.6.29

then run 'make' and see if libxml2 builds and installs?  Perhaps it
didn't re-run the configuration step after the patch...

If that doesn't work, I'll go ahead and probably get rid of the
'make install', and just copy the files over directly (that's what
Gumstix's fork of buildroot does, and they may have had an actual
reason for it).  Odd I can't reproduce your situation though.

-Brad

  reply	other threads:[~2007-08-07 12:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 15:10 [Buildroot] [patch] libxml2 fixes Brad House
2007-08-06 20:38 ` Ulf Samuelsson
2007-08-06 20:57   ` Brad House
2007-08-06 21:04     ` Ulf Samuelsson
2007-08-06 21:28       ` Brad House
2007-08-07  4:38 ` Hebbar
2007-08-07 12:08   ` Brad House [this message]
2007-08-07 12:21     ` Steven J. Hill
2007-08-08  0:03       ` Hebbar
2007-08-08  0:10         ` Brad House
2007-08-07 17:17 ` Ulf Samuelsson

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=46B860B5.8050205@mainstreetsoftworks.com \
    --to=brad@mainstreetsoftworks.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