mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] weird ptxdist -q -j go  problems
Date: Mon, 19 Mar 2018 10:11:09 +0100	[thread overview]
Message-ID: <1521450669.13487.50.camel@erwinrol.com> (raw)
In-Reply-To: <20180310000919.6kzstcxkgnyjk62b@pengutronix.de>

Hey Michael,

I have pulled that commit into my tree, and haven't seen the problem
again.

But I must say I didn't see the problem since I reported ist, you know
how it is with race conditions, one time you have them 10 times in a
row the next time it takes weeks to happen again. 

So I will keep an eye on it.

Thanks for the update,

Erwin


On Sat, 2018-03-10 at 01:09 +0100, Michael Olbrich wrote:
> Hi,
> 
> On Sun, Feb 25, 2018 at 04:12:04PM +0100, Erwin Rol wrote:
> > it happend again, and again with busybox. Maybe busybox also needs some
> > host tool that isn't build yet, cause I have not seen this error on non
> > -j builds. 
> > 
> > The logfiles have the following errors;
> 
> [...]
> 
> I managed to reproduce this once today. I think I figured out what happens.
> It's a rather tricky dependency issue. I've pushed a fix to master. Please
> test.
> 
> Regards,
> Michael
> 

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-03-19  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25  9:17 Erwin Rol
2018-02-25 10:38 ` Michael Olbrich
2018-02-25 10:56   ` Erwin Rol
2018-02-25 11:43     ` Michael Olbrich
2018-02-25 12:02       ` Erwin Rol
2018-02-25 12:30         ` Michael Olbrich
2018-02-25 15:12           ` Erwin Rol
2018-03-10  0:09             ` Michael Olbrich
2018-03-19  9:11               ` Erwin Rol [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:
  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=1521450669.13487.50.camel@erwinrol.com \
    --to=mailinglists@erwinrol.com \
    --cc=ptxdist@pengutronix.de \
    /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