From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0002914]: X11R7 fails to build with a fork bomb.
Date: Fri, 13 Jun 2008 08:58:10 -0700 [thread overview]
Message-ID: <695d6f64bc6e8487adbbcb1a47774911@bugs.uclibc.org> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=2914
======================================================================
Reported By: KHAksnes
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 2914
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 04-14-2008 04:35 PDT
Last Modified: 06-13-2008 08:58 PDT
======================================================================
Summary: X11R7 fails to build with a fork bomb.
Description:
X11R7 fails to build in a nasty way.
The package check is missing (As far as I understand this is
check.sourceforge.net) When ./configure in libxcb-1.1 tries to test for
this it starts a fork bomb making my development machine (a fedora 8
laptop) grind to a halt.
I am using a current buildroot. (svn at 21732)
======================================================================
----------------------------------------------------------------------
KHAksnes - 04-14-08 07:22
----------------------------------------------------------------------
Building of RPM shows the same behaviour. The fork bomb involves
pkg-config, glib-config and sed at least.
----------------------------------------------------------------------
KHAksnes - 04-14-08 07:31
----------------------------------------------------------------------
I forgot to mention that I was trying to build for i686 using, a fairly
standard setup with, kernel: 2.6.24, uclibc: 0.9.29, binutils:
2.18.50.0.1, gcc: 4.2.3, busybox: 1.10.
----------------------------------------------------------------------
KHAksnes - 05-26-08 04:54
----------------------------------------------------------------------
After meeting similar fork bombs several times I did som further research.
The problem seems to be pkg-config.
pkg-config have a builtin fallback to gnome-config. Sometimes when
pkg-config can't find its gnome-config fallback it forks out of control.
Installing the following shell script as staging_dir/usr/bin/gnome-config
fixes the problem
#! /bin/sh
exit 1
----------------------------------------------------------------------
KHAksnes - 06-13-08 08:58
----------------------------------------------------------------------
Bug hs ben reported upstream to the pkg-config developers.
Issue History
Date Modified Username Field Change
======================================================================
04-14-08 04:35 KHAksnes New Issue
04-14-08 04:35 KHAksnes Status new => assigned
04-14-08 04:35 KHAksnes Assigned To => buildroot
04-14-08 07:22 KHAksnes Note Added: 0006614
04-14-08 07:31 KHAksnes Note Added: 0006624
05-26-08 04:54 KHAksnes Note Added: 0007864
06-13-08 08:58 KHAksnes Note Added: 0008194
======================================================================
next reply other threads:[~2008-06-13 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 15:58 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-26 11:54 [Buildroot] [buildroot 0002914]: X11R7 fails to build with a fork bomb bugs at busybox.net
2008-04-14 14:31 bugs at busybox.net
2008-04-14 14:22 bugs at busybox.net
2008-04-14 11:35 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=695d6f64bc6e8487adbbcb1a47774911@bugs.uclibc.org \
--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