Re: [Cygwin] [Master] failure when compiling liblangtag

Eike Rathke <erack -AT- redhat.com>
Mon, 29 Apr 2013 18:27:41 +0200

Hi,

On Tuesday, 2013-04-16 15:44:28 +0200, Eike Rathke wrote:

Cc'ing Peter Foley who did the gcc-wrapper.


We now have the same failure with an upgrade to liblangtag-0.5.0, see
https://gerrit.libreoffice.org/3676 and the error log
https://ci.libreoffice.org/job/buildbot/663

Peter, what's going wrong there?

  Eike

-- 
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
For key transition see http://erack.de/key-transition-2013-01-10.txt.asc
Support the FSFE, care about Free Software! https://fsfe.org/support/?erack

Attachment: pgp41iPzDtZDg.pgp
Description: PGP signature

Context

[Cygwin] [Master] failure when compiling liblangtag · Mat M
- Re: [Cygwin] [Master] failure when compiling liblangtag · Michael Stahl
  - Re: [Cygwin] [Master] failure when compiling liblangtag · Mat M
    - Re: [Cygwin] [Master] failure when compiling liblangtag · Eike Rathke
      - Re: [Cygwin] [Master] failure when compiling liblangtag · Mat M
      - Re: [Cygwin] [Master] failure when compiling liblangtag · Eike Rathke
        
        Re: [Cygwin] [Master] failure when compiling liblangtag · Eike Rathke
        
        Re: [Cygwin] [Master] failure when compiling liblangtag · Eike Rathke
    - Re: [Cygwin] [Master] failure when compiling liblangtag · Christian Lohmaier

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.