Hi Diya,

If you are facing the same issue as mentioned at the link , let me tell you
that ICU is not part of the xercesc.3.1.1 source.
So please download ICU sources separately and build the ICU related libs. it
will be good if you create static libs of it.

Then while building the Xerces with ICU you will have to show the path of
ICU libs and I feel while running the configure/runConfigure script you will
have to provide the appropriate option and I feel path of ICU as well.  If
you have a look at the makefile which got generated please check if the icu
libs are being linked.

Hope this gives you a good idea about it.


Thanks and Regards
-Brijesh


On Thu, Aug 26, 2010 at 8:09 PM, diya das <[email protected]> wrote:

> Hi All,
>
>  I encountered the same issue as
>
> http://old.nabble.com/Could-not-load-a-transcoding-service---Linux-td25468057.html
>
> My target ARM-Linux board doesn not have gconv however I have
> cross-compiled
> Xerces for arm without ICU.
>
> Has anyone successfully cross-compiled ICU for the purpose of building
> Xerces
> with ICU to avoid dependency to native encoder.
> I am running into issues with ICU. I should probably be asking this
> question in
> the ICU mailing list.
>
>
> Boris mentioned in reply to the thread that he could build it though it is
> not
> easy Could you please give some pointers ?
>
> Thanks
>
>
>
> ----- Original Message ----
> From: Boris Kolpackov <[email protected]>
> To: [email protected]
> Sent: Tue, August 24, 2010 4:30:43 PM
> Subject: Re: ARM-Linux port
>
> Hi Diya,
>
> diya das <[email protected]> writes:
>
> > I have the same error that I mentioned previously even with the
> > --host option. Earlier I only had the CXX and CC paths in the
> > Configure command line.
>
> Then it must be a problem with your cross-compiler. The cross-
> compilation support in Xerces-C++ is definitely working; I
> cross-compiled it myself on multiple occasions.
>
> What you can try to do is check the config.log file for the
> source code of the test that configure is trying to compile
> as well as the compiler command line that it is executing
> and see why it doesn't work.
>
> Boris
>
> --
> Boris Kolpackov, Code Synthesis
> http://codesynthesis.com/~boris/blog
> Open-source XML data binding for C++
> http://codesynthesis.com/products/xsd
> XML data binding for embedded systems
> http://codesynthesis.com/products/xsde
> Command line interface to C++ compiler
> http://codesynthesis.com/projects/cli
>
>
>
>
>

Reply via email to