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


In nss, security/coreconf they reference e.g. Linux2.6.mk.  Building on 3.0.0 this fails because 
there is no Linux3.0.mk.

All that would be needed to fix this is copy Linux2.6.mk to Linux3.0.mk.

The workflow for your builds is unusual in that it unpacks the subsidiary tarballs and charges 
right into building things.  In a normal build workflow, you would have untar, possible patch, 
configure, possible patch, make.  In your workflow, there is no opportunity to get control back for 
even the simplest of workarounds.

If there is a way to do site-local patches in your workflow between the unpacking and the building 
steps, I haven't found it documented.  I beg you to think this over and decide to do something 
about it.

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.