mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist <ptxdist@pengutronix.de>
Subject: [ptxdist] weird ptxdist -q -j go  problems
Date: Sun, 25 Feb 2018 10:17:46 +0100	[thread overview]
Message-ID: <1519550266.13487.2.camel@erwinrol.com> (raw)

Hey all,

how wel is the -j option of ptxdist tested ? Is it used a lot by others
or is it more an obscure untested option ?

With the lastest version of ptxdist I wanted to try the -j option and
am running into weird problems. 

First I forgot to add a _CONF_TOOL setting in one of my *.make files,
and I found a file called "11" in my dir with the following content;

ptxdist: error: automatic prepare tool selection failed. Set <PKG>_CONF_TOOL

that "11" somehow sounds like it should have been a filedescriptor
number and not an actual file. 


Of course not having the _CONF_TOOL was an error from my side, after
fixing it it seemed to work.

But now the ptxdist -j -q go from time to time stops with an error. In
the log file it always seems to say something like;

}}} 2018-02-25T08:38:46+0000
/home/ANNAX.LOCAL/erro/Projects/ABE.centos7/bsps/Seco_E38XX_64/master/p
txdist/bin/ptxdist go -j -q; (exit value: 2)


I have seen this with busybox and openssl with different compilers
(x86_62 and armv5). It always is exit value: 2.

When I than do a ./ptdixt go again it happily continues (even if I use
-q -j) 

Any idea what is causing this? 

I hat this under Centos7 with a 24core and 32core machine. 

- Erwin


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2018-02-25  9:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25  9:17 Erwin Rol [this message]
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

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=1519550266.13487.2.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