From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] util-linux build time increase?
Date: Thu, 21 Feb 2019 10:38:08 -0800 [thread overview]
Message-ID: <1770058.feCM7Ylm5x@reaper> (raw)
In-Reply-To: <29348cc8-6a3b-3eed-fc72-7b9869c7a4ca@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On Thursday, February 21, 2019 1:36:24 AM PST Joshua Kinard wrote:
> Does anyone have an idea why util-linux's build time would go up
> significantly from 2.32.x to 2.33.x? It may be a MIPS thing, as my x86_64
> box shows no discernible change in build times between the same versions.
> Can any other archs check w/ genlop to see if they see a large jump in build
> time?
>
This may be related to this bug:
https://bugs.gentoo.org/447970
I have packages ( cpio and tar for example) that take hours to emerge on arm
boards with FEATURES=sandbox, and couple of minutes without.
./configure getcwd test takes unreasonably long time under sandbox.
don't have util-linux statistics to show.
--
Georgy Yakovlev
Gentoo Linux Developer
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-21 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 9:36 [gentoo-dev] util-linux build time increase? Joshua Kinard
2019-02-21 12:29 ` Guilherme Amadio
2019-02-21 21:18 ` Kristian Fiskerstrand
2019-02-28 9:16 ` Joshua Kinard
2019-03-01 14:43 ` Kristian Fiskerstrand
2019-02-21 18:38 ` Georgy Yakovlev [this message]
2019-02-25 8:58 ` Tobias Klausmann
2019-02-25 10:07 ` Alexander Tsoy
2019-02-25 10:18 ` Alexander Tsoy
2019-02-28 9:13 ` Joshua Kinard
2019-03-01 15:01 ` Mart Raudsepp
2019-03-03 9:22 ` Joshua Kinard
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=1770058.feCM7Ylm5x@reaper \
--to=gyakovlev@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kumba@gentoo.org \
/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