mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] weird ptxdist -q -j go  problems
Date: Sun, 25 Feb 2018 12:43:51 +0100	[thread overview]
Message-ID: <20180225114351.kfdzj4uri7klpjih@pengutronix.de> (raw)
In-Reply-To: <1519556207.13487.8.camel@erwinrol.com>

Hi,

On Sun, Feb 25, 2018 at 11:56:47AM +0100, Erwin Rol wrote:
> The build system is Centos7 with bash;
> GNU bash, version 4.2.46(2)-release (x86_64-redhat-linux-gnu)
> 
> Not the newest but on the other hand Centos7/RHEL7 is a very stable
> platform. It would be very nice if it could be part of the list of
> platforms Pengutronix uses to test ptxdist ;-)

I run build tests in several different chroots and Centos7 is one of them.
Unfortunately that one is currently broken, because it's missing Python 3.4
needed for meson :-/.

> > > 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) 
> > 
> > Can you send the relevant parts from the logfile? I know there is a
> > dependency problem in openssl. I cause very rare build errors. I've yet to
> > figure out the exact cause. It's not '-j' specific but that seems to
> > trigger it more often.
> > 
> > I'm not aware of any problems with busybox. A log with some more details
> > would be helpful.
> 
> I found a missing dependency for libsoup, it needs glib host tools. I
> am running from a minimal docker so those aren't available on the host
> and so libsoup.in needed select HOST_GLIB
> 
> Maybe it is just caused by some other missing deps. 

Some packages using glib also need host-glib for some of the helper tools
like glib-mkenums.

Can you send a patch? And please include the reason in the commit message.
Or the build error if it's useful. That helps while reviewing the
dependencies for the next update.

> BTW: wouldn't it be easier to add select HOST_GLIB to glib.in ? Or even
> more general do that for all packages that have a host-* version ?

Not all packages that use glib actually need host-glib and I'd like to
avoid unnecessary dependenciesa.

> I'll look into it and report back when I know more, certainly now I
> know -j really is a first class citizen :-)

I've spent quite some time to make '-j' work without problems and as fast
as possible without overloading the build server. All my ptxdist build
tests use it. I's most definitely a first class citizen.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-02-25 11:43 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 [this message]
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=20180225114351.kfdzj4uri7klpjih@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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