| View previous topic :: View next topic |
| Author |
Message |
leyvi
Apprentice
Joined: 08 Sep 2023
Posts: 181
|
 Posted: Sun Mar 09, 2025 2:45 pm Post subject: app-shells/bash pgo way too long |
 |
|
| I have a pretty fast PC, and app-shells/bash has been in the PGO stage of building for the last 3.5 hours. Is that normal, or should I try starting the build process again? |
|
| Back to top |
|
 |
Banana
Moderator
Joined: 21 May 2004
Posts: 1916
Location: Germany
|
|
| Back to top |
|
|
leyvi
Apprentice
Joined: 08 Sep 2023
Posts: 181
|
| Posted: Sun Mar 09, 2025 3:15 pm Post subject: |
|
|
Yeah, I confirmed with htop that everything is running. These are the last couple lines of the build log: | Code: | make[1]: Entering directory '/var/tmp/portage/app-shells/bash-5.2_p37/work/bash-5.2/builtins'
make[1]: warning: -j12 forced in submake: resetting jobserver mode.
***********************************************************
make[1]: 'pipesize.h' is up to date.
make[1]: Leaving directory '/var/tmp/portage/app-shells/bash-5.2_p37/work/bash-5.2/builtins'
* *
* GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* *
***********************************************************
declare -r SHELLOPTS="braceexpand:hashall:interactive-comments"
Testing /var/tmp/portage/app-shells/bash-5.2_p37/work/bash-5.2/bash
version: 5.2.37(1)-release
versinfo: 5 2 37 1 release x86_64-pc-linux-gnu
HOSTTYPE = x86_64
OSTYPE = linux-gnu
MACHTYPE = x86_64-pc-linux-gnu
Any output from any test, unless otherwise noted, indicates a possible anomaly
run-alias
run-appendop
run-arith
run-arith-for
run-array
warning: all of these tests will fail if arrays have not
warning: been compiled into the shell
warning: the BASH_ARGC and BASH_ARGV tests will fail if debugging support
warning: has not been compiled into the shell
run-array2
warning: all of these tests will fail if arrays have not
warning: been compiled into the shell
run-assoc
warning: all of these tests will fail if arrays have not
warning: been compiled into the shell
|
Also, here's the process tree: | Code: | UID PID PPID PGID SID C SZ RSS PSR STIME TTY TIME CMD
portage 6251 6248 6248 6248 0 656 1780 8 13:25 pts/3 00:00:00 [app-shells/bash-5.2_p37] sandbox /usr/lib/portage/python3.13/ebuild.sh compile
portage 6252 6251 6248 6248 0 2995 7380 0 13:25 pts/3 00:00:00 bash /usr/lib/portage/python3.13/ebuild.sh compile
portage 6273 6252 6248 6248 0 2996 6340 1 13:25 pts/3 00:00:00 bash /usr/lib/portage/python3.13/ebuild.sh compile
portage 7895 6273 6248 6248 0 2289 4696 9 13:25 pts/3 00:00:00 bash /usr/lib/portage/python3.13/ebuild-helpers/emake CFLAGS=-w -march=znver4 -mtune=znver4 -O3 -pipe -flto=full -std=gnu17 -fprofile-update=atomic -fprofile-dir=/var/tmp/portage/app
portage 7897 7895 6248 6248 0 1869 3692 1 13:25 pts/3 00:00:00 make -j12 -l12.0 CFLAGS=-w -march=znver4 -mtune=znver4 -O3 -pipe -flto=full -std=gnu17 -fprofile-update=atomic -fprofile-dir=/var/tmp/portage/app-shells/bash-5.2_p37/temp/pgo -fpro
portage 7971 7897 6248 6248 0 2157 4048 8 13:25 pts/3 00:00:00 /bin/sh -c ( cd ./tests && \ ?BUILD_DIR=/var/tmp/portage/app-shells/bash-5.2_p37/work/bash-5.2 PATH=/var/tmp/portage/app-shells/bash-5.2_p37/work/bash-5.2/tests:$PATH THIS_SH=/va
portage 7972 7971 6248 6248 0 2157 4244 7 13:25 pts/3 00:00:00 /bin/sh run-all
portage 8532 7972 6248 6248 0 2157 4080 5 13:25 pts/3 00:00:00 sh run-assoc
portage 8533 8532 6248 6248 0 2467 5116 2 13:25 pts/3 00:00:00 /var/tmp/portage/app-shells/bash-5.2_p37/work/bash-5.2/bash ./assoc.tests
portage 8561 8533 6248 6248 99 2435 5388 1 13:25 pts/3 03:57:46 /var/tmp/portage/app-shells/bash-5.2_p37/work/bash-5.2/bash ./assoc2.sub
|
|
|
| Back to top |
|
|
|
Portage & Programming
