Re: convert setup_native to gbuild and add to tail_build

"Peter Foley" <pefoley2 -AT- verizon.net>
Wed, 13 Feb 2013 17:15:13 -0500

Niko,

I just pushed a fix.
Can you see if it works now?

Thanks,

Peter

-----Original Message-----From: Niko Rönkkö

Sent: Wednesday, February 13, 2013 10:14 AM
To: libreoffice-dev
Cc: pefoley2@verizon.net
Subject: Re: convert setup_native to gbuild and add to tail_build

Hi!

This commit breaks my Mac build with error message:
Unrecognized option: -p
Usage: ulfconv [-o <output file>] [-t <encoding table>] [<ulf file>]

Problem seems to be on line 22 in CustomTarget_mac.mk:
http://opengrok.libreoffice.org/xref/core/setup_native/CustomTarget_mac.mk#22

--

RN

Context

[PATCH] convert setup_native to gbuild and add to tail_build · Peter Foley (via Code Review)
- [PUSHED] convert setup_native to gbuild and add to tail_build · David Ostrovsky (via Code Review)
- Re: [PATCH] convert setup_native to gbuild and add to tail_build · Andras Timar
  - Re: [PATCH] convert setup_native to gbuild and add to tail_build · Peter Foley
    - Re: [PATCH] convert setup_native to gbuild and add to tail_build · Andras Timar
      - Re: [PATCH] convert setup_native to gbuild and add to tail_build · Peter Foley
        
        Re: [PATCH] convert setup_native to gbuild and add to tail_build · Andras Timar
- Re: convert setup_native to gbuild and add to tail_build · Niko Rönkkö
  - Re: convert setup_native to gbuild and add to tail_build · Peter Foley
    - [SOLVED] Re: convert setup_native to gbuild and add to tail_build · Niko Rönkkö

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.