From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Claude <claude@cbcr.me>
Cc: crossgcc@sourceware.org
Subject: Re: ct-ng build hangs forever
Date: Thu, 27 Mar 2014 06:54:00 -0000 [thread overview]
Message-ID: <20140327075412.5ee3a638@skate> (raw)
In-Reply-To: <loom.20140327T021714-313@post.gmane.org>
Dear Claude,
On Thu, 27 Mar 2014 01:30:44 +0000 (UTC), Claude wrote:
> I tried different version of gmp. I also compiled it successfully standalone.
>
> I am not sure where to look now. Any pointer?
When the thing is eating 100% cpu and stuck, can you do a "ps auxf",
and give the output of the process tree that starts from the ct-ng
process? This way, we would see which thing is actually stuck. That
might help in giving a clue.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-03-27 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 1:35 Claude
2014-03-27 6:54 ` Thomas Petazzoni [this message]
2014-03-27 12:21 ` Claude
2014-03-29 17:39 ` Claude
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=20140327075412.5ee3a638@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=claude@cbcr.me \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).