Gentoo Forums :: View topic - Documenting USE="-*"

Documenting USE="-*"

View unanswered posts
View posts from last 24 hours

Goto page Previous 1, 2

Gentoo Forums Forum Index

Documentation, Tips & Tricks

View previous topic :: View next topic

Author

Message

Hu
Moderator

Joined: 06 Mar 2007
Posts: 21673

Posted: Sat Mar 23, 2024 9:19 pm Post subject:

CaptainBlood wrote:

USE="-* unicode" dev-lisp/clisp required to build here.

What fails when you do not set USE=unicode here? Is Portage currently requiring you to set that flag, or did you discover that USE=-unicode causes clisp to fail to build?

flexibeast
Guru
Guru

Joined: 04 Apr 2022
Posts: 325
Location: Naarm/Melbourne, Australia

Posted: Sun Mar 24, 2024 12:07 am Post subject:

CaptainBlood wrote:

USE="-* unicode" dev-lisp/clisp required to build here.

Sorry, could you clarify what you mean? i just successfully merged dev-lisp/clisp without needing to do anything specific or unusual with USE flags .... Do you mean that, to merge dev-lisp/clisp with USE="-*", one also needs to add 'unicode' to USE?

stefan11111
l33t
l33t

Joined: 29 Jan 2023
Posts: 922
Location: Romania

Posted: Tue Mar 26, 2024 1:30 pm Post subject:

CaptainBlood wrote:

USE="-* unicode" dev-lisp/clisp required to build here.

Thks 4 ur attention, interest & support.

Tested it here.
FIle a bug, either on the gentoo bugzilla or upstream.
_________________
My overlay: https://github.com/stefan11111/stefan_overlay
INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd /usr/lib/modules-load.d *udev* /usr/lib/tmpfiles.d *tmpfiles* /var/lib/dbus /usr/bin/gdbus /lib/udev"

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Tue Mar 26, 2024 2:56 pm Post subject:

stefan11111 wrote:

Tested it here.
FIle a bug, either on the gentoo bugzilla or upstream.

I guess I should, at least for the sake of USE=-* since it helps to have BETTER tested ebuilds in the portage tree.

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here.
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

Last edited by CaptainBlood on Tue Mar 26, 2024 4:09 pm; edited 1 time in total

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Tue Mar 26, 2024 3:33 pm Post subject:

Bugzilla Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here. LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Tue Mar 26, 2024 3:37 pm Post subject:

@flexibeast, Plz read OP for a better understanding of context... Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here. LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Tue Mar 26, 2024 4:01 pm Post subject:

Just noticed

Code:

emerge --info

removes '-*' in reported USE description here

sys-apps/portage seems to have no sympathy for the :twisted:

Come on portage don't do that... :oops:

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here.
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

sublogic
Apprentice

Joined: 21 Mar 2022
Posts: 222
Location: Pennsylvania, USA

Posted: Tue Mar 26, 2024 10:51 pm Post subject:

CaptainBlood wrote:

Just noticed

Code:

emerge --info

removes '-*' in reported USE description here

sys-apps/portage seems to have no sympathy for the :twisted:

Come on portage don't do that... :oops:

Thks 4 ur attention, interest & support.

It shows you what's left, not how you got there.

Code:

$ emerge --info | grep USE > junk1
$ USE='-*' emerge --info | grep USE > junk2
$ diff junk1 junk2
1c1
< USE="X a52 aac acl acpi alsa amd64 bluetooth branding bzip2 cairo cdda cdr cet crypt cups dbus dri dts dvd dvdr elogind encode exif flac gdbm gif gpm gtk gui iconv icu ipv6 jpeg lcms libnotify libtirpc lvm lzma mad mng mp3 mp4 mpeg multilib ncurses nls ogg opengl openmp pam pango pcre pdf png policykit ppds qt5 readline sdl seccomp sound spell split-usr ssl startup-notification svg test-rust tiff truetype udev udisks unicode upower usb vorbis vulkan wxwidgets x264 xattr xcb xft xml xv xvid zlib zstd" ABI_X86="64 32" ADA_TARGET="gcc_12" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx f16c mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" INPUT_DEVICES="libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-1" POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_11" PYTHON_TARGETS="python3_11" RUBY_TARGETS="ruby31" SANE_BACKENDS="epson2" VIDEO_CARDS="amdgpu radeonsi" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
---
> USE="amd64 split-usr test-rust" ABI_X86="64" ELIBC="glibc" KERNEL="linux"

flexibeast
Guru
Guru

Joined: 04 Apr 2022
Posts: 325
Location: Naarm/Melbourne, Australia

Posted: Wed Mar 27, 2024 12:58 am Post subject:

CaptainBlood wrote:

Plz read OP for a better understanding of context...

i did, and yet i still wondered what exactly you meant. Though to be fair, Hu's question - which you've not yet responded to - far better expressed what i was fundamentally wondering about.

(i tend to ask clarifying questions one at a time, because my experience is that asking more than one question often seems to result in people just pick one of the questions and only respond to that one.)

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Wed Mar 27, 2024 8:12 am Post subject:

@flexibeast

flexibeast wrote:

CaptainBlood wrote:

USE="-* unicode" dev-lisp/clisp required to build here.

i just successfully merged dev-lisp/clisp without needing to do anything specific or unusual with USE flags .... Do you mean that, to merge dev-lisp/clisp with USE="-*", one also needs to add 'unicode' to USE?

Since you already have dev-lisp/clisp, giving a try rebuilding with

Code:

"USE="-*" emerge -1 dev-lisp/clisp

should provide fruitful results within a couple of minutes, possibly less.

Alternatively

CaptainBlood wrote:

Bugzilla

should disambiguate...

flexibeast wrote:

Though to be fair, Hu's question - which you've not yet responded to - far better expressed what i was fundamentally wondering about.

quote button use as an efficient way to state a crystal clear position perhaps?

Out of curiosity, are you interested to migrate to USE="-*"?

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here.
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

flexibeast
Guru
Guru

Joined: 04 Apr 2022
Posts: 325
Location: Naarm/Melbourne, Australia

Posted: Wed Mar 27, 2024 11:14 pm Post subject:

CaptainBlood wrote:

quote button use as an efficient way to state a crystal clear position perhaps?

As previous posts of mine demonstrate, i regularly make use of the quote functionality. In this particular instance, for some reason i'd missed Hu's comment when writing my own. i occasionally miss stuff and make mistakes, because i'm human; sorry.

Quote:

Out of curiosity, are you interested to migrate to USE="-*"?

Not at all. i generally feel doing so is .... not the best idea, for various reasons. However:

* i spend a lot of my volunteer time writing documentation, including for things i don't use myself. (Not least because i hate the notion that forum discussions constitute 'documentation'.) Here are my contributions to the wiki so far, having started using Gentoo a couple of years ago. Previously, i contributed to the documentation for Void, and around that time i started my 'guides' collection.

* As i wrote in a previous comment upthread:

Quote:

i really appreciate people willing to experiment and break their system in order to determine what stuff is and isn't needed - one of the reasons i'm running Gentoo is to be able to minimise the amount of stuff on my system i know i don't actually need or use (for both maintenance and security reasons).

So even though i've often found the fundamentalist anti-bloat crowd to be rude, entitled, and demanding of the time of volunteers, i follow threads like these in order to try to clearly understand what's going on - which occasionally involves asking 'stupid' questions - so that i might be able to document it for others, regardless of whether it's relevant to me personally.

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Wed Mar 27, 2024 11:43 pm Post subject:

@flexibeast, I'm glad you seem to have found an answer to your question. Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here. LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Wed Mar 27, 2024 11:48 pm Post subject:

Any 23 profile migration experience to share anyone? Any thoughts specifics to care of because of USE="-"? Not ready yet here Thks 4 ur attention, interest & support. _________________ USE="- ..." in /etc/portage/make.conf here. LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

flexibeast
Guru
Guru

Joined: 04 Apr 2022
Posts: 325
Location: Naarm/Melbourne, Australia

Posted: Thu Mar 28, 2024 12:49 am Post subject:

CaptainBlood wrote:

@flexibeast, I'm glad you seem to have found an answer to your question.

Yes, by looking at the Bugzilla bug. Which means you could have just replied to my original question with: "Please refer to this bug report." You chose not to do so, and seem to not care about others' time. Okay; bye.

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Thu Mar 28, 2024 3:20 pm Post subject:

23.0 migration here.

Binutils
Flags

Code:

Installed versions: 2.41-r5(2.41)^t(16:09:47 18/02/2024)(gold gprofng pgo plugins zstd -cet -debuginfod -doc -hardened -multitarget -nls -static-libs -test -vanilla)

Code:

emerge --ask --oneshot sys-devel/binutils

Unchanged

Code:

[ebuild R ] sys-devel/binutils-2.41-r5

Fine here.

Gcc
Flags

Code:

Installed versions: 13.2.1_p20240210(13)^t(03:10:20 19/02/2024)(cxx fortran graphite jit lto multilib openmp pgo pie sanitize vtv zstd -ada -cet -custom-cflags -d -debug -default-stack-clash-protection -default-znow -doc -fixed-point -go -hardened -ieee-long-double -libssp -modula2 -nls -objc -objc++ -objc-gc -pch -ssp -systemtap -test -valgrind -vanilla)

Code:

emerge --ask --oneshot sys-devel/gcc

Changed

Code:

[ebuild R ] sys-devel/gcc-13.2.1_p20240210 USE="(default-stack-clash-protection*) (default-znow*)"

Fine here.

Glibc
Flags:

Code:

Installed versions: 2.38-r10(2.2)^t(11:57:45 02/03/2024)(multilib profile static-libs -audit -caps -cet -compile-locales -crypt -custom-cflags -doc -gd -hash-sysv-compat -headers-only -multiarch -multilib-bootstrap -nscd -perl -selinux -ssp -stack-realign -suid -systemd -systemtap -test -vanilla)

Code:

emerge --ask --oneshot sys-libs/glibc

Changed

Code:

[ebuild R ] sys-libs/glibc-2.38-r10

Code:

>>> Regenerating /etc/ld.so.cache...

Fine here.

env-update && source /etc/profile
Fine here

libool
Flags

Code:

Installed versions: 2.4.7-r4(2)(11:16:30 27/03/2024)(-vanilla)

Code:

emerge --ask --oneshot libtool

Fine here

Code:

emerge --empty-tree world

In progress...

To be continued...

Forecast:
USE=-* prevents repository without-systemd integration when running

Code:

emerge --ask --emptytree @world

GDH-gentoo
Veteran
Veteran

Joined: 20 Jul 2019
Posts: 1546
Location: South America

Posted: Thu Mar 28, 2024 3:29 pm Post subject:

CaptainBlood wrote:

Code:

[ebuild R ] sys-devel/gcc-13.2.1_p20240210 USE="(default-stack-clash-protection*) (default-znow*)"

Are those the USE flags that changed and you are omitting the other set flags from the output, or are those the only USE flags set? If it's the latter, the explosion should be fun...

* Grabs popcorn *
_________________

NeddySeagoon wrote:

I'm not a witch, I'm a retired electronics engineer

Ionen wrote:

As a packager I just don't want things to get messier with weird build systems and multiple toolchains requirements though

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Thu Mar 28, 2024 6:44 pm Post subject:

@GDH-gentoo, Got a real point. For both binutils & gcc there are from emerge -1 category/package. Just as provided in eselect read news. Previous post edited. * Grabs popcorn , Sympathy for the ? _________________ USE="- ..." in /etc/portage/make.conf here. LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

shimbob
Tux's lil' helper

Joined: 13 Sep 2003
Posts: 136

Posted: Tue Apr 09, 2024 5:28 am Post subject:

In the spirit of minimizing USE with "-*", how about adding these defaults to make.conf too?

Code:

USE_PYTHON=""
PYTHON_TARGETS=""
PYTHON_SINGLE_TARGET=""

and adding as required to package.env, of course.

For my use case (basic desktop, web, arduino, steam), of the 128 ebuilds that can use python, there's 18 that work fine without it.

stefan11111
l33t
l33t

Joined: 29 Jan 2023
Posts: 922
Location: Romania

Posted: Thu Apr 11, 2024 9:23 am Post subject:

CaptainBlood wrote:

Did you run into some sort of problem with USE="-*"?
I can't figure it out what exactly from your posts.
_________________
My overlay: https://github.com/stefan11111/stefan_overlay
INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd /usr/lib/modules-load.d *udev* /usr/lib/tmpfiles.d *tmpfiles* /var/lib/dbus /usr/bin/gdbus /lib/udev"

CaptainBlood
Advocate

Joined: 24 Jan 2010
Posts: 3632

Posted: Sat May 04, 2024 10:10 pm Post subject:

Initally build here!

Code:

qlop -tv sys-devel/gcc
2024-05-04T13:58:06 >>> sys-devel/gcc-13.2.1_p20240503: 4:31:18

and it's equery output!

Code:

equery u sys-devel/gcc
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for sys-devel/gcc-13.2.1_p20240503:
U I
- - ada : Build the ADA language (GNAT) frontend
- - cet : (Restricted to >=sys-devel/gcc-10)
Enable support for control flow hijacking protection. On amd64, this provides Intel
Control Flow Enforcement Technology (CET). On arm64, this provides Branch Target
Identification (BTI) and Pointer Authentication Code (PAC) support. This is only effective
on amd64 or arm64. Only provides benefits on newer CPUs. For Intel, the CPU must be at
least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless
on older CPUs, but provides no benefit either. For ARM64, PAC was introduced in armv8.3-a,
and BTI was introduced in armv8.5-a. When combined with USE=hardened on amd64, GCC will
set -fcf-protection by default when building software. The effect is minimal on systems
which do not support it, other than a possible small increase in codesize for the NOPs.
The generated code is therefore compatible with i686 at the earliest. On arm64, GCC will
set -mbranch-protection=standard by default when building software.
- - d : Enable support for the D programming language
- - debug : Enables GCC's 'checking' facility via --enable-checking=yes,extra,rtl. This adds checks to
various compiler passes for integrity and input validation. This can help catch possible
miscompilations early as well as latent bugs which could become real problems in future,
but at the cost of slower compile times when using GCC. Unrelated to backtraces.
- - doc : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package
instead of globally
+ + fortran : Add support for fortran
- - go : Build the GCC Go language frontend.
+ + graphite : Add support for the framework for loop optimizations based on a polyhedral intermediate
representation
- - hardened : Activate default security enhancements for toolchain (gcc, glibc, binutils)
+ + jit : Enable libgccjit so other applications can embed gcc for Just-In-Time compilation.
+ + lto : Build using Link Time Optimizations (LTO). Note that GCC is always built with support for
building other programs with LTO. This USE flag is for whether GCC itself is built and
optimized with LTO.
- - modula2 : Build the GCC Modula-2 language frontend.
- - nls : Add Native Language Support (using gettext - GNU locale utilities)
- - objc : Build support for the Objective C code language
- - objc++ : Build support for the Objective C++ language
- - objc-gc : Build support for the Objective C code language Garbage Collector
+ + openmp : Build support for the OpenMP (support parallel computing), requires >=sys-devel/gcc-4.2
built with USE="openmp"
+ + pgo : Build GCC using Profile Guided Optimization (PGO). GCC will build itself and then analyze
the just-built binary and then rebuild itself using the data obtained from analysis of
codepaths taken. It does not affect whether GCC itself supports PGO when building other
software. This substantially increases the build time needed for building GCC itself.
+ + sanitize : Build support for various sanitizer functions (ASAN/TSAN/etc...) to find runtime problems
in applications.
- - ssp : Build packages with stack smashing protection on by default
- - systemtap : enable systemtap static probe points
- - test : Enable dependencies and/or preparations necessary to run tests (usually controlled by
FEATURES=test but can be toggled independently)
- - valgrind : Enable annotations for accuracy. May slow down runtime slightly. Safe to use even if not
currently using dev-debug/valgrind
- - vanilla : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE
as the severity of the meaning changes drastically
+ + vtv : Build support for virtual table verification (a C++ hardening feature). This does not
control whether GCC defaults to using VTV> Note that actually using VTV breaks ABI and
hence the whole system must be built with -fvtable-verify.
+ + zstd : Enable support for ZSTD compression

Now binary package

Code:

ls /var/cache/binpkgs/sys-devel/gcc
gcc-13.2.1_p20240503-1.gpkg.tar

which installed elsewhare:

Code:

qlop -tv sys-devel/gcc
2024-05-05T00:03:24 >>> sys-devel/gcc-13.2.1_p20240503: 1′50″

which equery outputs differently:

Code:

equery u sys-devel/gcc
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for sys-devel/gcc-13.2.1_p20240503:
U I
- - ada : Build the ADA language (GNAT) frontend
- - cet : (Restricted to >=sys-devel/gcc-10)
Enable support for control flow hijacking protection. On amd64, this
provides Intel Control Flow Enforcement Technology (CET). On arm64,
this provides Branch Target Identification (BTI) and Pointer
Authentication Code (PAC) support. This is only effective on amd64 or
arm64. Only provides benefits on newer CPUs. For Intel, the CPU must
be at least as new as Tiger Lake. For AMD, it must be at least as new
as Zen 3. This is harmless on older CPUs, but provides no benefit
either. For ARM64, PAC was introduced in armv8.3-a, and BTI was
introduced in armv8.5-a. When combined with USE=hardened on amd64,
GCC will set -fcf-protection by default when building software. The
effect is minimal on systems which do not support it, other than a
possible small increase in codesize for the NOPs. The generated code
is therefore compatible with i686 at the earliest. On arm64, GCC will
set -mbranch-protection=standard by default when building software.
- - d : Enable support for the D programming language
- - debug : Enables GCC's 'checking' facility via
--enable-checking=yes,extra,rtl. This adds checks to various compiler
passes for integrity and input validation. This can help catch
possible miscompilations early as well as latent bugs which could
become real problems in future, but at the cost of slower compile
times when using GCC. Unrelated to backtraces.
- + default-stack-clash-protection : Build packages with stack clash protection on by default as a
hardening measure. This enables -fstack-clash-protection by default
which protects against large memory allocations allowing stack
smashing. May cause slightly increased codesize, but modern compilers
have been adapted to optimize well for this case, as this mitigation
is now quite common. See https://developers.redhat.com/blog/2020/05/2
2/stack-clash-mitigation-in-gcc-part-3 and
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt.
- + default-znow : Request full relocation on start from ld.so by default. This sets the
-z,now (BIND_NOW) flag by default on all linker invocations. By
resolving all dynamic symbols at application startup, parts of the
program can be made read-only as a hardening measure. This is closely
related to RELRO which is also separately enabled by default. In some
applications with many unresolved symbols (heavily plugin based, for
example), startup time may be impacted.
- - doc : Add extra documentation (API, Javadoc, etc). It is recommended to
enable per package instead of globally
+ + fortran : Add support for fortran
- - go : Build the GCC Go language frontend.
+ + graphite : Add support for the framework for loop optimizations based on a
polyhedral intermediate representation
- - hardened : Activate default security enhancements for toolchain (gcc, glibc,
binutils)
+ + jit : Enable libgccjit so other applications can embed gcc for Just-In-Time
compilation.
+ + lto : Build using Link Time Optimizations (LTO). Note that GCC is always
built with support for building other programs with LTO. This USE
flag is for whether GCC itself is built and optimized with LTO.
- - modula2 : Build the GCC Modula-2 language frontend.
- - nls : Add Native Language Support (using gettext - GNU locale utilities)
- - objc : Build support for the Objective C code language
- - objc++ : Build support for the Objective C++ language
- - objc-gc : Build support for the Objective C code language Garbage Collector
+ + openmp : Build support for the OpenMP (support parallel computing), requires
>=sys-devel/gcc-4.2 built with USE="openmp"
+ + pgo : Build GCC using Profile Guided Optimization (PGO). GCC will build
itself and then analyze the just-built binary and then rebuild itself
using the data obtained from analysis of codepaths taken. It does not
affect whether GCC itself supports PGO when building other software.
This substantially increases the build time needed for building GCC
itself.
+ + sanitize : Build support for various sanitizer functions (ASAN/TSAN/etc...) to
find runtime problems in applications.
- - ssp : Build packages with stack smashing protection on by default
- - systemtap : enable systemtap static probe points
- - test : Enable dependencies and/or preparations necessary to run tests
(usually controlled by FEATURES=test but can be toggled
independently)
- - valgrind : Enable annotations for accuracy. May slow down runtime slightly. Safe
to use even if not currently using dev-debug/valgrind
- - vanilla : Do not add extra patches which change default behaviour; DO NOT USE
THIS ON A GLOBAL SCALE as the severity of the meaning changes
drastically
+ + vtv : Build support for virtual table verification (a C++ hardening
feature). This does not control whether GCC defaults to using VTV>
Note that actually using VTV breaks ABI and hence the whole system
must be built with -fvtable-verify.
+ + zstd : Enable support for ZSTD compression

Digging a little reveals on the building system:

Code:

{ada cet custom-cflags +cxx d debug default-stack-clash-protection default-znow doc fixed-point +fortran go graphite hardened ieee-long-double jit libssp lto modula2 multilib +nls +nptl objc objc++ objc-gc (+)openmp (+)pch pgo +pie rust +sanitize +ssp systemtap test valgrind vanilla vtv zstd}
Installed versions: 13.2.1_p20240503(13)^t(18:26:09 04/05/2024)(cxx default-stack-clash-protection default-znow fortran graphite jit lto multilib openmp pgo pie sanitize vtv zstd -ada -cet -custom-cflags -d -debug -doc -fixed-point -go -hardened -ieee-long-double -libssp -modula2 -nls -objc -objc++ -objc-gc -pch -ssp -systemtap -test -valgrind -vanilla)

Please note USE="default-stack-clash-protection default-znow" aren't defaulted to.

As far as this early sys-devel/gcc-13.2.1_p20240503 build is concerned, we now have a USE=-* proof portage package.
Can't help thinking on M$ 'We know better' paradigm. i must be in a grumpy mood today.

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here.
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

Display posts from previous:

	Gentoo Forums Forum Index Documentation, Tips & Tricks	All times are GMT Goto page Previous 1, 2
Page 2 of 2

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy