This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Infinite loop in eglibc-2.18 cross build for private port
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Konstantin Vladimirov <konstantin dot vladimirov at gmail dot com>
- Cc: "libc-ports at sourceware dot org" <libc-ports at sourceware dot org>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Sat, 26 Apr 2014 13:25:25 -0400
- Subject: Re: Infinite loop in eglibc-2.18 cross build for private port
- Authentication-results: sourceware.org; auth=none
- References: <CADn89gTx8yzcgsGQqrunaDPiLY7L6qt4qGikZSZh5pfnsDP-JQ at mail dot gmail dot com>
On Fri, Apr 25, 2014 at 8:58 AM, Konstantin Vladimirov
<konstantin.vladimirov@gmail.com> 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.
Cheers,
Carlos.