public inbox for
 help / color / mirror / Atom feed
From: Konstantin Vladimirov <>
Subject: Infinite loop in eglibc-2.18 cross build for private port
Date: Fri, 25 Apr 2014 12:58:00 -0000	[thread overview]
Message-ID: <> (raw)


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

Scheme is (skipping long paths, gcc arguments and sed magic lines):

1) make[2]: Entering directory `eglibc-2.18/libc/csu'
2) /usr/bin/install -c -m 644 ../include/limits.h ...
3) gawk -f ../scripts/gen-as-const.awk tlsdesc.sym \
    | gcc -S -o tlsdesc.hT3 ... -x c -  -MD -MP  -MF tlsdesc.h.dT -MT
tlsdesc.h.d tlsdesc.h
4) sed -n 's/...' tlsdesc.hT3 > tlsdesc.hT
5) rm -f tlsdesc.hT3
6) sed -e 's@ ... ' -e 's@  ...' tlsdesc.h.dT > tlsdesc.h.dT2
7) rm -f tlsdesc.h.dT
8) mv -f tlsdesc.h.dT2 tlsdesc.h.d
9) mv -f tlsdesc.hT tlsdesc.h
10) make[2]: Leaving directory `eglibc-2.18/libc/csu'

after that build system enters csu folder again and those 10 steps
repeats again and again.

On step 10, tlsdesc.h looks meaningful and filled with correct information.

I really stuck in attempts to find this bug. I suppose something wrong
in my port, but I can not even imagine what can I do to reveal such

If anyone faced similar problems and has an experience like this, any
help, or even advice "where to look" will be appreciated.

With best regards, Konstantin

             reply	other threads:[~2014-04-25 12:58 UTC|newest]

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

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 \ \ \ \ \

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