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 13:30:25 +0100 [thread overview]
Message-ID: <20180225123025.ccmuicxzr6hyknl3@pengutronix.de> (raw)
In-Reply-To: <1519560178.13487.10.camel@erwinrol.com>
Hi,
On Sun, Feb 25, 2018 at 01:02:58PM +0100, Erwin Rol wrote:
> On Sun, 2018-02-25 at 12:43 +0100, Michael Olbrich 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 :-/.
>
> install devtoolset-6, this is what I install in my centos7 docker;
>
> RUN \
> echo 'Upgrading all system packages to the latest available versions' >&2 && \
> yum -y install epel-release && \
> yum -y install centos-release-scl && \
> yum -y install devtoolset-6 && \
> yum -y update
>
> RUN \
> echo 'Installing host tools and build system functionality' >&2 && \
> yum -y install \
[...]
Thanks for the hint. I know that there are multiple ways to install Python
3.4 on Centos7 but I wasn't sure which one I should use. Picking one that
someone already uses in combination with PTXdist sounds like a good idea.
Now I just need to find the time to properly integrate this...
> > 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.
>
> I will have to break it again to get the error msg :-) I'll see if I
> find some time later today.
That would be great, thanks.
> > > 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 see if I can find some time to do
> ./ptxdist clean; ./ptxdist compile pkg_that_uses_glib
> to see what builds and waht doesn't.
>
> Of course that is going to cost a lot of build time, so it might take a
> while to get done.
I know. It makes systematic tests like this difficult.
> > > 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.
>
> That is good, cause those "configure" stages take for ever :-)
Exactly, and when I combined -jiX with -jeX then my colleagues complained
when the compile jobs overloaded the build server. So I started looking for
a solution and came up with the mechanism behind -j.
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
next prev parent reply other threads:[~2018-02-25 12:30 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 [this message]
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=20180225123025.ccmuicxzr6hyknl3@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