Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 13.09.2011 11:09, Stephan Bergmann wrote:
On 09/13/2011 01:00 AM, Norbert Thiebaud wrote:
On Mon, Sep 12, 2011 at 4:53 PM, Michael Stahl<mst@openoffice.org>  wrote:
On 12.09.2011 23:26, Peter Foley wrote:
--- a/MathMLDTD/prj/build.lst
+++ b/MathMLDTD/prj/build.lst
@@ -1,3 +1,2 @@
-md   MathMLDTD       :       solenv NULL
-md   MathMLDTD                                                       usr1    -       all     
md_mkout NULL
-md   MathMLDTD\prj                                           get             -       all     
md_prj NULL
+md   MathMLDTD       : NULL

you remove the dependency on solenv; it seems that currently we don't
have any module (except solenv of course, and "testautomation" which
doesn't do anything) that does not directly or indirectly depend on
solenv; i wonder why that is?  is there perhaps some reason that modules
must depend on solenv?

isn't that for the basic setup of solver ? (mkdir od bin inc etc..)
but I believe Deliver.mk do the mkdir by precaution anyways.. so that
should no have any impact here..

But that might explain the strange tinderbox failure at 
<b>, 
a missing 350minor.mk early one, where xml2cmp is one of the first three 
modules being built (in parallel).

-Stephan

thanks for reminding me, 3X0minor.mk was the thing that i only vaguely
remembered.  apparently it's still necessary in converted modules
because we start gmake indirectly via dmake.

guess somebody should put back the solenv deps :)


Context


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.