| View previous topic :: View next topic |
| Author |
Message |
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
 Posted: Sat Apr 12, 2025 12:28 pm Post subject: should i make any changes in make.conf |
 |
|
i jsut wanted to know if i should make any changes for make.conf to either decrease complie time or some how more optmize it for my hardware, and yes i know alot of the useflags are redeudant as they should be covered by the profile, and the the ccache dosen't really do much
| Code: |
c2@gentoobtw ~ $ fastfetch
-/oyddmdhs+:. c2@gentoobtw
-odNMMMMMMMMNNmhy+-` ------------
-yNMMMMMMMMMMMNNNmmdhy+- OS: Gentoo Linux x86_64
`omMMMMMMMMMMMMNmdmmmmddhhy/` Kernel: Linux 6.14.2-gentoo-dist
omMMMMMMMMMMMNhhyyyohmdddhhhdo` Uptime: 22 mins
.ydMMMMMMMMMMdhs++so/smdddhhhhdm+` Packages: 1868 (emerge), 6 (flatpak-user)
oyhdmNMMMMMMMNdyooydmddddhhhhyhNd. Shell: bash 5.2.37
:oyhhdNNMMMMMMMNNNmmdddhhhhhyymMh Display (XV275K): 3840x2160 @ 60 Hz (as 3072x1728) in 27" [External]
.:+sydNMMMMMNNNmmmdddhhhhhhmMmy Display (Odyssey G7): 3840x2160 @ 120 Hz in 31" [External, HDR] *
/mMMMMMMNNNmmmdddhhhhhmMNhs: DE: KDE Plasma 6.3.4
`oNMMMMMMMNNNmmmddddhhdmMNhs+` WM: KWin (Wayland)
`sNMMMMMMMMNNNmmmdddddmNMmhs/. WM Theme: Infinity-Solid-Aurorae-6
/NMMMMMMMMNNNNmmmdddmNMNdso:` Theme: Breeze (Custum_blues_and_purples) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
+MMMMMMMNNNNNmmmmdmNMNdso/- Icons: Vivid-Dark-Icons [Qt], Vivid-Dark-Icons [GTK2/3/4]
yMMNNNNNNNmmmmmNNMmhs+/-` Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
/hMMNNNNNNNNMNdhs++/-` Cursor: Vivid-Dark-Icons (24px)
`/ohdmmddhys+++/:.` Terminal: konsole 24.12.3
`-//////:--. CPU: AMD Ryzen 7 7800X3D (16) @ 5.05 GHz
GPU: AMD Radeon RX 7900 XTX [Discrete]
Memory: 10.23 GiB / 93.94 GiB (11%)
Swap: 0 B / 16.00 GiB (0%)
Disk (/): 847.54 GiB / 914.07 GiB (93%) - xfs
Disk (/run/media/hdd): 8.35 TiB / 10.83 TiB (77%) - ext4
Disk (/run/media/nvme2): 120.24 GiB / 232.88 GiB (52%) - btrfs
Disk (/run/media/ssds): 52.07 GiB / 476.46 GiB (11%) - xfs
Local IP (wlp11s0): 192.168.4.161/22
Locale: en_US.UTF-8
c2@gentoobtw ~ $ cat /etc/portage/make.conf
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
COMMON_FLAGS="-march=native -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
ACCEPT_LICENSE="*"
RUST_FLAGS="-C opt-level=2"
LC_MESSAGES=C.utf8
MAKEOPTS="-j14"
EMERGE_DEFAULT_OPTS="--jobs 14"
VIDEO_CARDS=" amdgpu radeonsi"
ABI_X86="64 32"
USE="dist-kernel initramfs udisks encode lm-sensors plasma qt6 vaapi discord vulkan wayland alsa pipewire systemd aom dav1d svt-av1 vpx x264 x265 fdk-aac libmp3lame libvorbis libopus ffmpeg -gtk -gnome qt vlc aac faad fdk mp4 -openrc systemd-boot rocm -cuda openmp kde hip man colord osmesa hdr hip amr amrenc lame openmpt flac speex zimg shaderc snappy jack opencl vdpau drm"
CPU_FLAGS_X86="aes avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2 avx512_vnni avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f avx512ifma avx512vbmi avx512vl f16c fma3 mmx mmxext pclmul popcnt rdrand sha sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 vpclmulqdq"
L10N="en en-US ja"
FEATURES="parallel-fetch parallel-install ccache"
CCACHE_DIR="/run/media/ssds/ccache/"
CCACHE_SIZE="300G"
DISTDIR=/run/media/ssds/distfiles
PORTAGE_TMPDIR="/run/media/ssds/tmp"
PORTDIR_OVERLAY="/usr/local/portage/overlay"
LLVM_TARGETS="X86 AMDGPU"
c2@gentoobtw ~ $ cat .bashrc
# /etc/skel/.bashrc
#
# This file is sourced by all *interactive* bash shells on startup,
# including some apparently interactive shells such as scp and rcp
# that can't tolerate any output. So make sure this doesn't display
# anything or bad things will happen !
# Test for an interactive shell. There is no need to set anything
# past this point for scp and rcp, and it's important to refrain from
# outputting anything in those cases.
if [[ $- != *i* ]] ; then
# Shell is non-interactive. Be done now!
return
fi
# Put your fun stuff here.
alias update='sudo taskset -c 0-13 emerge -avfuDN @world && sudo taskset -c emerge -vuDN @world'
alias preupdate='sudo taskset -c 0-13 emerge -avfuDN @world'
alias updatenow='sudo taskset -c 0-13 emerge -avuDN @world'
alias ls='ls -A'
alias we='sudo watch -c -t -n 5 genlop -c'
alias emerge='sudo taskset -c 0-13 emerge'
#alias sudo emerge='sudo taskset -c 0-13 emerge'
c2@gentoobtw ~ $
|
|
|
| Back to top |
|
 |
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5614
Location: Bavaria
|
|
| Back to top |
|
|
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
| Posted: Sat Apr 12, 2025 12:50 pm Post subject: Re: should i make any changes in make.conf |
|
|
yeah i know thats why i did this in bashrc
| Code: |
alias update='sudo taskset -c 0-13 emerge -avfuDN @world && sudo taskset -c emerge -vuDN @world'
alias preupdate='sudo taskset -c 0-13 emerge -avfuDN @world'
alias updatenow='sudo taskset -c 0-13 emerge -avuDN @world'
alias ls='ls -A'
alias we='sudo watch -c -t -n 5 genlop -c'
alias emerge='sudo taskset -c 0-13 emerge'
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55175
Location: 56N 3W
|
| Posted: Sat Apr 12, 2025 12:58 pm Post subject: |
|
|
c2,
| Code: | MAKEOPTS="-j14"
EMERGE_DEFAULT_OPTS="--jobs 14" |
That allows make to start 196 threads each needing 2G RAM. Your system will become very slow or appear to lock up before it gets close to that.
With | Code: | | Memory: 10.23 GiB / 93.94 GiB |
you could consider putting the portage build space into RAM ... that's tmpfs.
It won't be any faster as the kernel will cache everything it can but it will save writes that will never be read. That's good for SSD write life.
Depending on how you tune | Code: | MAKEOPTS="-j14"
EMERGE_DEFAULT_OPTS="--jobs 14" |
you may need to allow big packages to build on disk.
ccache can be a very bad thing. It slows down the first build of a package, while the cache is written.
Subsequent builds are speeded up and every now and again, it causes things to break. Sympathy is minimal for ccache induced breakage.
Hopefully | Code: | | LLVM_TARGETS="X86 AMDGPU" |
does nothing as LLVM_TARGETS= are all forced on. The targets cannot reliably be built indepentently
| Code: | | [ebuild R ] llvm-core/llvm-20.1.1:20/20.1::gentoo USE="binutils-plugin libffi zstd -debug (-debuginfod) -doc -exegesis -libedit -test -verify-sig -xml -z3" LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" 0 KiB |
The ( ) means forced by your profile.
If you really want to use | Code: | | LLVM_TARGETS="X86 AMDGPU" |
you need to undo the forcing first then pick up the pieces afterwards.
It's your Gentoo your way. :)
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5614
Location: Bavaria
|
| Posted: Sat Apr 12, 2025 1:03 pm Post subject: |
|
|
With your taskset command you set the CPU affinity of a new command with a given CPU affinity, but it does not change the behavior of a program. If a program starts 20 threads, these are simply assigned to this CPU ... but still started.
BTW: It is highly recommended to NOT use "sudo". Change with "su -" to root user and do all emerges as root (it is the environment which could cause problems).
_________________
https://wiki.gentoo.org/wiki/User:Pietinger |
|
| Back to top |
|
|
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
| Posted: Sat Apr 12, 2025 2:18 pm Post subject: |
|
|
| NeddySeagoon wrote: | c2,
| Code: | MAKEOPTS="-j14"
EMERGE_DEFAULT_OPTS="--jobs 14" |
That allows make to start 196 threads each needing 2G RAM. Your system will become very slow or appear to lock up before it gets close to that.
With | Code: | | Memory: 10.23 GiB / 93.94 GiB |
you could consider putting the portage build space into RAM ... that's tmpfs.
It won't be any faster as the kernel will cache everything it can but it will save writes that will never be read. That's good for SSD write life.
Depending on how you tune | Code: | MAKEOPTS="-j14"
EMERGE_DEFAULT_OPTS="--jobs 14" |
you may need to allow big packages to build on disk.
ccache can be a very bad thing. It slows down the first build of a package, while the cache is written.
Subsequent builds are speeded up and every now and again, it causes things to break. Sympathy is minimal for ccache induced breakage.
Hopefully | Code: | | LLVM_TARGETS="X86 AMDGPU" |
does nothing as LLVM_TARGETS= are all forced on. The targets cannot reliably be built indepentently
| Code: | | [ebuild R ] llvm-core/llvm-20.1.1:20/20.1::gentoo USE="binutils-plugin libffi zstd -debug (-debuginfod) -doc -exegesis -libedit -test -verify-sig -xml -z3" LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" 0 KiB |
The ( ) means forced by your profile.
If you really want to use | Code: | | LLVM_TARGETS="X86 AMDGPU" |
you need to undo the forcing first then pick up the pieces afterwards.
It's your Gentoo your way.  |
so what should i set the make options and jobes to, i've never seen it use more then 50 gb of ram, i want to be able to complie large packages like the rocm kerrnel and llvm with 14 threads but i also want to be able to do mutiple smaller packages at once ex: the kde plasma suite. the thing rarely ever complies more then 4 medium sized packages at the same time and almost away a max of 8 for a smaller packages
yeah i just relized i was being stupid i had tmpfs setup and i un did it by setting the tmp dir to the ssds with out thinking about it much, also i don't really carea bout those, it's a raid 0 array for 2 sata ssds i got for free at micro center
i mainly have ccache so i can stop compling so i can do something resource entsive and have emerge pick back up to where it was.
also the llvm targets did effect a package i think it was one of the rust ones but i know i added it as i saw it as a valid flag that was disabled for a package i already have installed, and what do you mean by llvm targets are forced on i don't understand |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2941
|
| Posted: Sat Apr 12, 2025 2:43 pm Post subject: |
|
|
You should not use make.conf for use settings storage. They're should be only a few flags there. For example I have 4. Systemd should be set by your profile. Also I'm pretty sure you don't need vdpau.
There's /etc/portage/package.use for that.
Best Regards,
Georgi |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55175
Location: 56N 3W
|
| Posted: Sat Apr 12, 2025 2:54 pm Post subject: |
|
|
c2,
| Code: | | LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" |
The () around "(AArch64) (AMDGPU) (ARM) ... means forced by your profile
Here it means forced on. Were it "(-AArch64) (-AMDGPU) (-ARM) ... it would be forced off.
It means that you cannot affect LLVM_TARGETS by setting LLVM_TARGETS in /etc/portage/* The setting is ignored.
If you really want to choose your own LLVM_TARGETS, its a two step process.
1. Undo the ().
2. Set LLVM_TARGETS=
The () can apply to any USE flags
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55175
Location: 56N 3W
|
| Posted: Sat Apr 12, 2025 2:57 pm Post subject: |
|
|
logrusx,
As the man with the wooden leg said, its a matter of a pinion. :)
I set USE flags I want to apply to everything in make.conf and per package USE flags in package.use.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2941
|
| Posted: Sat Apr 12, 2025 3:35 pm Post subject: |
|
|
| Neddy, it's a matter of opinion until you are forced to change it :) |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5614
Location: Bavaria
|
| Posted: Sat Apr 12, 2025 3:37 pm Post subject: |
|
|
| NeddySeagoon wrote: | | I set USE flags I want to apply to everything in make.conf and per package USE flags in package.use. |
I do it the same way and I believe that @logrusx meant it that way too, because he wrote: “They're should be only a few flags there. For example I have 4”
c2,
some of your use-flags are already set by choosing the right profile (you have KDE installed so you probably have a Plasma profile active; this already sets “qt6,kde and many more; no need to set them again). If you want to know which ones, then simply comment out the line “USE=...” from your make.conf and then check with “emerge --info” which use-flags are still globally active (then of course activate the line in make.conf again).
Yes, our AMD64 Handbook recommends to set the use-flag “distkernel” globally in make.conf:
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Post-install.2Fupgrade_tasks
Regarding “initramfs” just read this message:
https://www.gentoo.org/support/news-items/2024-05-17-dracut-ext-kmods.html
_________________
https://wiki.gentoo.org/wiki/User:Pietinger |
|
| Back to top |
|
|
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3605
|
| Posted: Sat Apr 12, 2025 4:10 pm Post subject: |
|
|
| logrusx wrote: | You should not use make.conf for use settings storage. They're should be only a few flags there. For example I have 4. Systemd should be set by your profile. Also I'm pretty sure you don't need vdpau.
There's /etc/portage/package.use for that.
Best Regards,
Georgi |
I like making pretty much everything global.
Because if I enable some flag on one package, and it pulls in a new dependency... I might as well let the other packages access it too.
Exceptions do happen, sometime have to resolve some conflict etc, but overall this approach has been working fine for me. With dozens of USE flags enabled this way. The obvious downside is it often causes multiple rebuilds when I change something, so it increases compilation time. The opposite of what the OP wanted.
_________________
Make Computing Fun Again |
|
| Back to top |
|
|
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
| Posted: Sat Apr 12, 2025 9:51 pm Post subject: |
|
|
| NeddySeagoon wrote: | c2,
| Code: | | LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" |
The () around "(AArch64) (AMDGPU) (ARM) ... means forced by your profile
Here it means forced on. Were it "(-AArch64) (-AMDGPU) (-ARM) ... it would be forced off.
It means that you cannot affect LLVM_TARGETS by setting LLVM_TARGETS in /etc/portage/* The setting is ignored.
If you really want to choose your own LLVM_TARGETS, its a two step process.
1. Undo the ().
2. Set LLVM_TARGETS=
The () can apply to any USE flags |
so is this what i should do?
| Code: |
LLVM_TARGETS="(X86) (AMDGPU)"
|
[/quote] |
|
| Back to top |
|
|
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
| Posted: Sat Apr 12, 2025 9:54 pm Post subject: |
|
|
and what should i set EMERGE_DEFAULT_OPTS and MAKEOPTS to to get the best prefromance (i want it to use 14 threads max( i an fine with using taskset to deal with it))
but dose having this
| Code: |
MAKEOPTS="-j14"
EMERGE_DEFAULT_OPTS="--jobs 14"
|
causes any issues other then high ram useage taskset to hard limit emerge to 14 threads, should i use load avreage or something like that |
|
| Back to top |
|
|
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
| Posted: Sat Apr 12, 2025 10:15 pm Post subject: |
|
|
| c2 wrote: | | NeddySeagoon wrote: | c2,
| Code: | | LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" |
The () around "(AArch64) (AMDGPU) (ARM) ... means forced by your profile
Here it means forced on. Were it "(-AArch64) (-AMDGPU) (-ARM) ... it would be forced off.
It means that you cannot affect LLVM_TARGETS by setting LLVM_TARGETS in /etc/portage/* The setting is ignored.
If you really want to choose your own LLVM_TARGETS, its a two step process.
1. Undo the ().
2. Set LLVM_TARGETS=
The () can apply to any USE flags |
so is this what i should do?
| Code: |
LLVM_TARGETS="(X86) (AMDGPU)"
|
|
[/quote]
so doing that did this
| Code: |
[ebuild R ~] dev-lang/rust-1.85.1:1.85.1::gentoo USE="(-big-endian) -clippy -debug -dist -doc (-llvm-libunwind) -lto -rust-analyzer -rust-src -rustfmt -system-llvm -test -verify-sig -wasm" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="sse2" LLVM_SLOT="(19)" LLVM_TARGETS="(X86) -AArch64 -AMDGPU* -ARC -ARM -AVR -BPF -CSKY -DirectX -Hexagon -Lanai -LoongArch -M68k -MSP430 -Mips -NVPTX -PowerPC -RISCV -SPIRV -Sparc -SystemZ -VE -WebAssembly -XCore -Xtensa" 0 KiB
|
so i'm going to turn it back |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5614
Location: Bavaria
|
|
| Back to top |
|
|
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
| Posted: Sat Apr 12, 2025 11:07 pm Post subject: |
|
|
| pietinger wrote: | | c2 wrote: | | [...] should i use load avreage or something like that |
YES. 
 |
kk |
|
| Back to top |
|
|
c2
n00b
Joined: 14 Mar 2025
Posts: 32
|
| Posted: Sat Apr 12, 2025 11:11 pm Post subject: |
|
|
so this is good
| Code: |
LC_MESSAGES=C.utf8
MAKEOPTS="-j14 -l14"
EMERGE_DEFAULT_OPTS="--jobs 14 --load-average=14"
|
|
|
| Back to top |
|
|
freke
Veteran
Joined: 23 Jan 2003
Posts: 1072
Location: Somewhere in Denmark
|
| Posted: Sun Apr 13, 2025 1:20 am Post subject: |
|
|
| c2 wrote: | so this is good
| Code: |
LC_MESSAGES=C.utf8
MAKEOPTS="-j14 -l14"
EMERGE_DEFAULT_OPTS="--jobs 14 --load-average=14"
|
|
I would remove the --jobs 14 (14 ebuilds running at the same time) - each job can spawn 14 threads (-j14), probably not what you want.
(if I'm understanding -j and --jobs somewhat correctly) |
|
| Back to top |
|
|
bstaletic
Guru
Joined: 05 Apr 2014
Posts: 494
|
| Posted: Sun Apr 13, 2025 1:48 am Post subject: |
|
|
| c2 wrote: |
so is this what i should do?
| Code: |
LLVM_TARGETS="(X86) (AMDGPU)"
|
|
No. Read man 5 portage, especially the part about package.use.mask and package.use.force (and their stable counterparts).
Then use that knowledge to "unforce" the default flags.
Only then will LLVM_TARGETS in your make.conf do anything. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2941
|
| Posted: Sun Apr 13, 2025 4:28 am Post subject: |
|
|
| bstaletic wrote: | | c2 wrote: |
so is this what i should do?
| Code: |
LLVM_TARGETS="(X86) (AMDGPU)"
|
|
No. Read man 5 portage, especially the part about package.use.mask and package.use.force (and their stable counterparts).
Then use that knowledge to "unforce" the default flags.
Only then will LLVM_TARGETS in your make.conf do anything. |
OP doesn't need to do anything about LLVM_TARGETS. Just remove them from make.conf.
Best Regards,
Georgi |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2941
|
| Posted: Sun Apr 13, 2025 4:32 am Post subject: |
|
|
People, OP isn't clear about make.conf. That's why s/he is asking us. Please think the bigger picture before giving advice and keep to the best practices.
Also what somebody else does which is outside of best practices can only bring confusion. No need to mention it here.
Best Regards,
Georgi |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55175
Location: 56N 3W
|
| Posted: Sun Apr 13, 2025 10:28 am Post subject: |
|
|
c2,
You should not attempt to change LLVM_TARGETS=. It's been set by the Gentoo devs as the targets are not independent, as the LLVM_TARGETS would have you believe.
is probably better than a poke in the eye with a sharp stick but not all build systems honour MAKEOPTS=, so it may not do what you want all the time.
Don't do | Code: | | EMERGE_DEFAULT_OPTS="--jobs 14" |
Its always possible to run and look at the list of things to be built, then decide on --jobs.
Thus do the build with | Code: | | emerge -uDUav --jobs=X ... |
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Portage & Programming
... I guess you really don't want this. Maybe have a look into: