Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0005364]: fontconfig compilations sometimes failed with parallel build
Date: Mon, 13 Oct 2008 03:34:41 -0700	[thread overview]
Message-ID: <a1ce8abaaee3775a2943eff0eb2e8322@busybox.net> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=5364 
====================================================================== 
Reported By:                tpetazzoni
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   5364
Category:                   Other
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             10-13-2008 03:15 PDT
Last Modified:              10-13-2008 03:34 PDT
====================================================================== 
Summary:                    fontconfig compilations sometimes failed with
parallel build
Description: 
fontconfig is affected by a compile bug that only occurs from time to time
when parallel compilation is enabled. The bug is described at
https://bugs.freedesktop.org/show_bug.cgi?id=16464.

The attached patch includes the fix for fontconfig in buildroot. However,
it modifies a Makefile.am file, so running automake is needed, but I'm not
sure Buildroot will do that automatically (as the bug only occurs
sometimes, it's quite hard to test whether the fix properly works or
not).

====================================================================== 

---------------------------------------------------------------------- 
 tpetazzoni - 10-13-08 03:34  
---------------------------------------------------------------------- 
After testing, it seems that patching Makefile.am is not sufficient to
re-run automake.

What should be done in this case ? Provide a patch that also fixes the
generated Makefile ? Run automake before compiling fontconfig ? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-13-08 03:15  tpetazzoni     New Issue                                    
10-13-08 03:15  tpetazzoni     Status                   new => assigned     
10-13-08 03:15  tpetazzoni     Assigned To               => buildroot       
10-13-08 03:15  tpetazzoni     File Added: parallel-compilation-fix.patch       
            
10-13-08 03:34  tpetazzoni     Note Added: 0013434                          
======================================================================

             reply	other threads:[~2008-10-13 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 10:34 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-20 15:02 [Buildroot] [buildroot 0005364]: fontconfig compilations sometimes failed with parallel build bugs at busybox.net
2008-10-13 10:15 bugs at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a1ce8abaaee3775a2943eff0eb2e8322@busybox.net \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox