Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ross.burton@arm.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/4] glibc: remove obsolete parallelism flag handling
Date: Thu, 06 Aug 2026 09:47:41 +0100	[thread overview]
Message-ID: <8a97f9a75449a32975930615f1e16d2b0491235c.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260805160320.41908-2-ross.burton@arm.com>

On Wed, 2026-08-05 at 17:03 +0100, Ross Burton via lists.openembedded.org wrote:
> Several problems here: the comment refers to PARALLELMFLAGS (which is a
> variable in glibc's Makefile) but the actual assignment is to
> EGLIBCPARALLELISM, which is an eglibc-ism and thus not respected by
> glibc. Thus we were emptying PARALLEL_MAKE and so not actually doing the
> build in parallel.
> 
> The Makefiles as of glibc 2.44[1] actually build in parallel well using
> the standard way to pass flags, so drop all of this logic.
> 
> On my machine this has noticable improvements to walltime:
> 
>   do_compile:  86s -> 44s
>   do_install:  55s -> 40s
> 
> Note that there is a PARALLELMFLAGS variable in the Makefiles, but using
> it has marginal gains over not and upstream are looking at removing it
> entirely.
> 
> [1] glibc 7cac99621e ("Makefile: Run the subdirectory recursion in parallel")
> 
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
>  meta/recipes-core/glibc/glibc.inc | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/meta/recipes-core/glibc/glibc.inc b/meta/recipes-core/glibc/glibc.inc
> index 560ebef677c..27a911dd8ff 100644
> --- a/meta/recipes-core/glibc/glibc.inc
> +++ b/meta/recipes-core/glibc/glibc.inc
> @@ -29,13 +29,6 @@ CACHED_CONFIGUREVARS:append:mipsarch = " libc_cv_ld_gnu_indirect_function=no"
>  GLIBC_EXTRA_OECONF ?= ""
>  GLIBC_EXTRA_OECONF:class-nativesdk = ""
>  
> -# glibc uses PARALLELMFLAGS variable to pass parallel build info so transfer
> -# PARALLEL_MAKE into PARALLELMFLAGS and empty out PARALLEL_MAKE
> -EGLIBCPARALLELISM := "PARALLELMFLAGS="${PARALLEL_MAKE}""
> -EXTRA_OEMAKE[vardepsexclude] += "EGLIBCPARALLELISM"
> -EXTRA_OEMAKE += "${EGLIBCPARALLELISM}"
> -PARALLEL_MAKE = ""
> -
>  # glibc make-syscalls.sh has a number of issues with /bin/dash and
>  # it's output which make calls via the SHELL also has issues, so
>  # ensure make uses /bin/bash
> 


Unfortunately
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4399
is full of what look like parallel make failures :(

Cheers,

Richard


  reply	other threads:[~2026-08-06  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 16:03 [PATCH 1/4] oeqa/selftest/glibc: remove obsolete parallel make assignment Ross Burton
2026-08-05 16:03 ` [PATCH 2/4] glibc: remove obsolete parallelism flag handling Ross Burton
2026-08-06  8:47   ` Richard Purdie [this message]
2026-08-05 16:03 ` [PATCH 3/4] glibc: remove obsolete shell override for make-syscalls.sh Ross Burton
2026-08-05 16:03 ` [PATCH 4/4] glibc: remove obsolete KSHELL assignment Ross Burton

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=8a97f9a75449a32975930615f1e16d2b0491235c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    /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