From: Brad House <brad@mainstreetsoftworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] libxml2 fixes
Date: Mon, 06 Aug 2007 17:28:08 -0400 [thread overview]
Message-ID: <46B79268.1010908@mainstreetsoftworks.com> (raw)
In-Reply-To: <03ab01c7d86f$43b6ee60$dcc4af0a@atmel.com>
>>> When I tried to build libxml2 using a toolchain without wchar support
>>> it failed, when it is built with a toolchain supporting wchar, it completes the build.
>> When was this?
>
> 2-3 weeks ago.
>
>> and with what version of libxml2?
>
> libxml2 version from buildroot.
>
>> and on what architecture?
>
>
> generic-arm architecture.
>
>> On x86 and arm, that is not the case from my experience.
>> Can you also provide some more information on the actual error message?
>
> I killed that toolchain, so I do not have the error handy
> You can easily generate a new gcc-4.2.0/binutils-2.17 toolchain based on uClibc 0.29 without wchar
> for generic-arm.
Perhaps the rest of my patch resolved those issues as I am unable to recreate
your issue when using my patch. I just verified that I do NOT have BR2_USE_WCHAR
enabled (Toolchain Options ---> Enable WCHAR support is NOT checked). I could not
get libxml2 to compile at all without apply patches, but it didn't give any
issues related to wchar that I could see, it was because it was trying to build
stuff like the python module ...
-Brad
next prev parent reply other threads:[~2007-08-06 21:28 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 [this message]
2007-08-07 4:38 ` Hebbar
2007-08-07 12:08 ` Brad House
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=46B79268.1010908@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 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.