public inbox for
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <>
To: Konstantin Vladimirov <>
Cc: "" <>,
		"" <>
Subject: Re: Infinite loop in eglibc-2.18 cross build for private port
Date: Sat, 26 Apr 2014 17:25:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Apr 25, 2014 at 8:58 AM, Konstantin Vladimirov
<> wrote:
> I am working on private port for eglibc-2.18, cross-build (host system
> is x86, target system is private)
> I detected strange behavior in build system -- if build was
> interrupted (say by Ctrl+C) and then again started (and only in this
> case, regular rebuild works ok), then it loops infinitely on generated
> headers, like tlsdesc.h (it may loop on any, depending on time when
> Ctrl-C is pressed, say on tcb-offsets.h).

I've never seen anything like this. The subsequent question is: Who
cares? Just clean the build and start again? Your x86* based
cross-build environment should be so fast that it doesn't matter.

The bug in question could be a make bug, could be a flawed target we
fixed in a later release, or just about anything. The only solution is
brute-force debug the make output in verbose mode and see why the
target is circular.


      reply	other threads:[~2014-04-26 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 12:58 Konstantin Vladimirov
2014-04-26 17:25 ` Carlos O'Donell [this message]

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:

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

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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).