Re: libicudata in non-standard directory linking issues.

2012-06-26 Thread Norbert Thiebaud
On Mon, Jun 25, 2012 at 4:48 PM, Michael Stahl wrote: >> On 22 June 2012 09:57, Jonathan Adams wrote: i'm not sure if adding a defined(__IBMC__) etc. is the right approach but if it doesn't break anything... >>> >>> they added that line for z/OS ... which, I may be wrong, I believe to >

Re: libicudata in non-standard directory linking issues.

2012-06-25 Thread Michael Stahl
On 25/06/12 12:38, Jonathan Adams wrote: > yeah, that compiled icu fine, and I didn't even have to copy the icu > libs to the solver ... great! > compiled for a long time after that ... > > tools_test fails though ... > > If you can look through the "debug" file (sorry 1.7Mb > https://docs.goog

Re: libicudata in non-standard directory linking issues.

2012-06-25 Thread Jonathan Adams
yeah, that compiled icu fine, and I didn't even have to copy the icu libs to the solver ... compiled for a long time after that ... tools_test fails though ... If you can look through the "debug" file (sorry 1.7Mb https://docs.google.com/open?id=0B6o_jmGQm0dWd3VMWEc5alhJaWc ) and give me pointer

Re: libicudata in non-standard directory linking issues.

2012-06-22 Thread Jonathan Adams
> i'm not sure if adding a defined(__IBMC__) etc. is the right approach > but if it doesn't break anything... they added that line for z/OS ... which, I may be wrong, I believe to be an IBM system ... looking around wikipedia; I found references to what defines are set when compiling on z/OS ...

Re: libicudata in non-standard directory linking issues.

2012-06-21 Thread Michael Stahl
On 21/06/12 16:54, Jonathan Adams wrote: > umm ... it's 14Mb worth of patch ... oh, I've compiled 4.0.1 (i wonder > how I got to that version ...) ... downloading and working through > 49.1.2 ... > > compiled ... > > running a "check" ... > > [All tests passed successfully...] > Elapsed Time: 00

Re: libicudata in non-standard directory linking issues.

2012-06-21 Thread Jonathan Adams
umm ... it's 14Mb worth of patch ... oh, I've compiled 4.0.1 (i wonder how I got to that version ...) ... downloading and working through 49.1.2 ... compiled ... running a "check" ... [All tests passed successfully...] Elapsed Time: 00:00:24.619 Ok, applying to the in-tree icu ... not quite the

Re: libicudata in non-standard directory linking issues.

2012-06-21 Thread Michael Stahl
On 20/06/12 00:15, Jonathan Adams wrote: > to get icu working on Openindiana/Illumos/Solaris ... > > http://bugs.icu-project.org/trac/ticket/9390 > > I downloaded the very latest icu4c from icu-project and then worked > through the source till I compiled it ... :) > > I put a patch on their bug

Re: libicudata in non-standard directory linking issues.

2012-06-19 Thread Jonathan Adams
to get icu working on Openindiana/Illumos/Solaris ... http://bugs.icu-project.org/trac/ticket/9390 I downloaded the very latest icu4c from icu-project and then worked through the source till I compiled it ... :) I put a patch on their bug system to get it to compile on Solaris ... although someo

Re: libicudata in non-standard directory linking issues.

2012-06-19 Thread Eike Rathke
Hi Jonathan, On Tuesday, 2012-06-19 17:55:09 +0100, Jonathan Adams wrote: > Having had trouble getting icu compiled on Solaris with GCC, I > compiled it out of tree and placed it in /opt/icu on my computer (I > want to know what specifically needs to attach to non-standard > libraries on my syste

Re: libicudata in non-standard directory linking issues.

2012-06-19 Thread Caolán McNamara
On Tue, 2012-06-19 at 17:55 +0100, Jonathan Adams wrote: > I have an issue with compiling tail_build on certain > modules because they redefine the LD)LIBRARY_PATH: > > S=/home/sal/LibreOffice/libo && O=$S/solver/unxsogi && > W=$S/workdir/unxsogi && LD_LIBRARY_PATH="$O/lib" > > can anyone tell m

libicudata in non-standard directory linking issues.

2012-06-19 Thread Jonathan Adams
Having had trouble getting icu compiled on Solaris with GCC, I compiled it out of tree and placed it in /opt/icu on my computer (I want to know what specifically needs to attach to non-standard libraries on my system for portability) however I noticed that although LibreOffice is happy to know it