Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building hangs on a RHEL 6 machine
Date: Tue, 20 Sep 2011 17:35:21 +0200	[thread overview]
Message-ID: <20110920173521.498d8647@skate> (raw)
In-Reply-To: <CAJbs9BHpm3Tm-0eEA1gH-qqZf1WSnt7ny=tDuPOROocBGFLMgw@mail.gmail.com>

Hello,

Le Tue, 20 Sep 2011 11:16:27 -0400,
Rishi <rishid+mailman@gmail.com> a ?crit :

> I am trying to build a uclibc toolchain on a Redhat 6 machine and it
> hangs. The last lines printed have been reproduced below:
> 
> The config file I am using has been attached, I built the exact same
> config file just fine on a Ubuntu 10.04 machine but my work uses
> Redhat and need to be able to build it there.  The pertinent options
> are: Buildroot toolchain, Kernel headers, 2.6.36.x, uClibc v0.9.32.x
> and default config file.
> 
> Any thoughts?

Can you post the relevant part of the "ps auxf" command executed when
the Buildroot build hangs ? I.e, the part of the process tree that
starts at the main Buildroot make command. This will allow us to see on
which process/step the build process is hanging.

I guess Redhat 6 is now publicly available, so we cannot reproduce the
problem. Do you reproduce the problem with publicly available operating
systems, such as CentOS, so that we can reproduce ?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-09-20 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJbs9BHXcxhVOCoSKFykn1TEXw=DeJCRPExkNy94h-DPOUVm+g@mail.gmail.com>
2011-09-20 15:16 ` [Buildroot] Building hangs on a RHEL 6 machine Rishi
2011-09-20 15:35   ` Thomas Petazzoni [this message]
2011-09-20 15:38     ` Thomas Petazzoni
2011-09-20 16:53       ` Rishi
2011-09-20 17:14         ` Rishi

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=20110920173521.498d8647@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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