Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build

Michael Stahl <mst -AT- openoffice.org>
Tue, 13 Sep 2011 11:40:45 +0200

On 13.09.2011 11:33, Stephan Bergmann wrote:

On 09/13/2011 11:20 AM, Stephan Bergmann wrote:

On 09/13/2011 11:18 AM, Michael Stahl wrote:

guess somebody should put back the solenv deps :)


doing it right now


<http://cgit.freedesktop.org/libreoffice/core/commit/?id=9f78448b94288883d0b33d8ef372dc67a1903b31>

-Stephan


looks like the Mesa module also has the problem, can you fix that as well?

Context

[Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Peter Foley
- Re: [Libreoffice] [PUSHED][PATCH] convert MathMLDTD to gbuild and add to tail_build · Norbert Thiebaud
- Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Michael Stahl
  - Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Norbert Thiebaud
    - Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Stephan Bergmann
      - Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Michael Stahl
        
        Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Stephan Bergmann
        
        Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Stephan Bergmann
        
        Re: [Libreoffice] [PATCH] convert MathMLDTD to gbuild and add to tail_build · Michael Stahl

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.