Re: Build issue with system icu version

Eike Rathke <erack -AT- redhat.com>
Thu, 11 May 2017 13:58:18 +0200

Hi David,

On Wednesday, 2017-05-10 09:06:13 +0200, David Ostrovsky wrote:

Building LO on OpenSUSE 42.2, against the latest available system
icu version (52.1) is failing here with:
[...]
/usr/bin/genbrk: can not initialize ICU.  status = U_FILE_ACCESS_ERROR


Does  ldd /usr/bin/genbrk   show any peculiarity?
If not, then does this? i.e. output should be identical
make cmd cmd='ldd /usr/bin/genbrk'

Specifically check that libicudata.so.52 can be loaded.

  Eike

-- 
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
Care about Free Software, support the FSFE https://fsfe.org/support/?erack

Attachment: signature.asc
Description: PGP signature

Context

Build issue with system icu version · David Ostrovsky
- Re: Build issue with system icu version · Eike Rathke
  - Re: Build issue with system icu version · David Ostrovsky
    - Re: Build issue with system icu version · Eike Rathke
      - Re: Build issue with system icu version · David Ostrovsky
        
        Re: Build issue with system icu version · Eike Rathke
        
        Re: Build issue with system icu version · Tomáš Chvátal
        
        Re: Build issue with system icu version · Eike Rathke
        Re: Build issue with system icu version · Eike Rathke
        Re: Build issue with system icu version · David Ostrovsky

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.