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


Hi,

On Thu, Feb 09, 2012 at 09:23:56PM +0000, Michael Meeks wrote:
commit 6055a5df7b6e7452987a9584d10f436ca2d349fd
Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
Date:   Fri Oct 7 16:40:22 2011 +0200

    no more gbuild loops: break early on nonexistent objects (this commit
    breaks multi-repo support)

      could it be this one ? that introduces a good few wildcards ? it's odd -
by the time we get to here:

That should be easy to find out: just comment out the lines added by that
commit and see if it gets better. Those added lines should do nothing on a
healthy build. However, if someone adds an nonexisting file to compile, they
prevent make from looping endlessly, which is IIRC a sideeffect of

commit dfde3d1f8bd347c79b1f69ac9dac487229af6357
Author: Michael Stahl <mst@openoffice.org>
Date:   Fri Apr 15 17:27:07 2011 +0000

    gnumake4: #i117845#: LinkTarget.mk: refactor dep-files: [hg:371ab623e90d]

replacing of the ifneq ($(wildcard ...)) with an -include. If that is indeed the
case, Id propose offhand:
- get rid of the wildcard calls from 6055a5df7b6e7452987a9584d10f436ca2d349fd
- use the wildcard again in dfde3d1f8bd347c79b1f69ac9dac487229af6357
  (which is per link target and not per cxx file)

As everything with deps for dep generation is quite tricky, this might need
some more thought though.


Best,

Bjoern

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.