Re: [Libreoffice] Build failing in tail_build module

Caolán McNamara <caolanm -AT- redhat.com>
Wed, 24 Aug 2011 11:36:21 +0100

On Tue, 2011-08-23 at 21:41 +0200, Cor Nouws wrote:

Cor Nouws wrote (23-08-11 20:57)

Might have something to do with the version of make 3.81 in combination
with with-num-cpus larger then 1


I knew I had seen a mail about that.
Found it in the archives:
http://lists.freedesktop.org/archives/libreoffice/2011-August/016470.html 
;-)


Didn't Norbert add
http://cgit.freedesktop.org/libreoffice/core/diff/configure.in?id=d64bbd6bf8d41604e3f14f911f2169f4295e4d99
which on the face of it looks like it would warn you that you are using
make 3.81 and either auto-dial down the -jX to -j1 or tell you you're
doomed if you have an explicit --with-num-cpu used ?

C.

Context

[Libreoffice] Build failing in tail_build module · swagat sharma
- Re: [Libreoffice] Build failing in tail_build module · Cor Nouws
  - (message not available)
    - (message not available)
      - (message not available)
        
        Re: [Libreoffice] Build failing in tail_build module · Cor Nouws
        
        Re: [Libreoffice] Build failing in tail_build module · Cor Nouws
        
        Re: [Libreoffice] Build failing in tail_build module · Caolán McNamara
        
        Re: [Libreoffice] Build failing in tail_build module · Jonathan Aquilina
- Re: [Libreoffice] Build failing in tail_build module · Jenei Gábor
- Re: [Libreoffice] Build failing in tail_build module · Bjoern Michaelsen

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.