| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
I need to do some more. Revert my earlier changes for now.
Reverts: 97069fd8721ea55980e548b9cf1d55e2a234a514
Reverts: 0a0b2fe6aadb9d0c3b41fdabb21535659c839bf5
Reverts: 1b5d47858780c700e706582aa370a69148552055
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
Followup followup to 0a0b2fe6aadb9d0c3b41fdabb21535659c839bf5 and
1b5d47858780c700e706582aa370a69148552055.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
| |
Followup to 1b5d47858780c700e706582aa370a69148552055.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
Same sort of thing as 434a6775ce93a15ef517478565a938aa73d1d528 although
the paths are different as we're using something from libexec (gnat1).
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
I continue to mix up how tc_version_is_at_least works. One day I'll
change it...
Closes: https://bugs.gentoo.org/944007
Fixes: f6a974f8f2378c6c6a83345c101afce233fdf1d7
Fixes: b923a4c0d1a330e40f0a05f3bc94bb4f32ce1cbb
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Reported by ulm. This was introduced by a last-minute simplification I made,
but USE=libdiagnostics only exists for 9999 and the *next* snapshot, not
the current one, but even then, the code was wrong for < 15 as the use_enable
part was run unconditionally w/ USE=jit.
Fixes: b923a4c0d1a330e40f0a05f3bc94bb4f32ce1cbb
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
See https://gcc.gnu.org/wiki/libdiagnostics. New shared library for
diagnostics in GCC. Also provides the 'sarif-replay' tool.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removing the read bit from suid binaries has questionable security
benefit, and may cause problems for some software.
Instead of clobbering the entire file mode, just toggle the suid bit if
needed. In most cases this will result in a world-readable file.
Introduce the FCAPS_DENY_WORLD_READ setting for users who insist on
having their suid binaries unreadable.
Skip calling chown/chmod if the owner/mode is empty. This may be used by
ebuild authors in certain use cases.
Bug: https://bugs.gentoo.org/938164
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I was seriously mistaken on this: `1 file changed, 2228 deletions(-)` when
testing dropping it.
-g ultimately causes many more matches because of debug statements
and it confuses so many tests.
I must have just made an error when testing other big test flag changes
around the time.
This reverts commit 7200aecb3db3b2dd91129e1530bcb75ce096af91.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
RUST_NEEDS_LLVM and RUST_MULTILIB incorrectly had
ECLASS_VARIABLE in lowercase, resulting in these variables
not ending up in documentation.
Closes: https://bugs.gentoo.org/943559
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
d6cb7a61dad7e9672a8448597835dbbf9b9e0ccf removed the check that passed
--enable-cet or --disable-cet to configure making the script fallback to
automagic. The goal was to prevent passing --enable-cet on x86 gnu
triples as that would lead to gcc failing to build under crossdev. Note
that this specific crossdev cet issue has been solved in crossdev by
package.use.mask'ing the cet USE flag for gcc on x86 but targets
configured before that can still have the cet USE flag enabled.
Bug: https://bugs.gentoo.org/943332
Signed-off-by: Andrei Horodniceanu <a.horodniceanu@proton.me>
Closes: https://github.com/gentoo/gentoo/pull/39300
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Change _get_rust_slot to default to -b/BROOT.
Reuse _get_rust_slot result in pkg_setup.
Pass along arguments from get_rust_prefix to _get_rust_slot.
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
Closes: https://github.com/gentoo/gentoo/pull/39298
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove enable_cet_for 'i[34567]86' 'gnu' 'cet' from to prevent -fcf-protection on x86
systens where CET support will never be fully enabled anyway.
This should help with bug #933772 also but I was unable to reproduce to confirm.
Closes: https://bugs.gentoo.org/943332
Bug: https://bugs.gentoo.org/933772
Thanks-to: Sam James <sam@gentoo.org>
Signed-off-by: Ian Jordan <immoloism@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/940905
Signed-off-by: Nowa Ammerlaan <nowa@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The simplified dependency specification for cases where no RUST_MAX_SLOT
is set is the desired end state, however the edge case where portage
drops blockers with `--keep-going` has an unfortunate interaction where
both packages are installed simultaneously, e.g. dev-lang/rust-1.82.0:stable
and dev-lang/rust-1.82.0:1.82.0, and there's no easy way for end users
to resolve that as the legacy (though masked) ebuilds will meet the simple
Rust dependency.
Both packages install rlibs with different hashes in them to the same
path (as shown below) resulting in failures when a package attempts
to link against an rlib and finds two.
1.82.0: .../x86_64-unknown-linux-gnu/lib/libunwind-fc4fe814489209c6.rlib
1.82.0-r100: .../x86_64-unknown-linux-gnu/lib/libunwind-ab65e6747cbe4a5a.rlib
Bug: https://bugs.gentoo.org/943143
Bug: https://bugs.gentoo.org/943206
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Users setting up kernel module signing are instructed by our and upstream
documentation to use the kernels x509.genkey config file. This ensures that
a supported key is generated.
However, in the current situation users will first have to emerge
gentoo-sources or similar to actually get this genkey file. This is inconvenient
so lets just install the genkey config file in our dist-kernels.
There are also some other tools, scripts, and lists that may be useful, so while
we are changing this anyway lets just install all of those as well and in the
process simplify the code.
Signed-off-by: Nowa Ammerlaan <andrewammerlaan@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
The open-ended dependency (no `RUST_MAX_VER`) was generated
before `usedep` was set to anything. Define `usedep` when
the variable is initialised and let the `RUST_NEEDS_LLVM`
path set it per llvm slot as required.
Closes: https://bugs.gentoo.org/943289
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Inherit llvm-r1 where required and let it die if LLVM_COMPAT is not
set.
- New variable: RUST_MULTILIB; if set will generate a multilib usedep
for supported rust slots.
- RUST_USEDEP -> RUST_REQ_USE to be consistent with other eclasses
(ebuild updates handled in a followup commit).
- Tidyup & address feedback
- Improve RUST_MIN_VER (only) dependency specification
Closes: https://bugs.gentoo.org/943206
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
A quick sanity check that `CARGO` is set in appropriate cargo_src_*
phase functions will make it easier for users to catch occurrences
where pkg_setup does not call rust_pkg_setup.
Also inherit llvm-r1 if required and let it die instead of us if
the environment is not properly setup.
Closes: https://bugs.gentoo.org/943147
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Like we do for arm64 and amd64, diverge from the upstream check for
linux and only enable it for gnu triples.
Closes: https://bugs.gentoo.org/942951
Signed-off-by: Andrei Horodniceanu <a.horodniceanu@proton.me>
Closes: https://github.com/gentoo/gentoo/pull/39228
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
The check was negated meaning that RUST_MIN_VER would only be set when
it was not required.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To better match the behaviour of the legacy virtual/rust package,
update generated dependency strings so that dev-lang/rust-bin is
output before dev-lang/rust.
In the longer term it is expected that this will be reverted
to the original order (prefer dev-lang/rust) as users that
particularly care about this also have the option of selecting
an appropriate binpkg.
When selecting an installed Rust to use the non-bin package is
still preferred over the -bin if both are installed.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
| |
Followup to 583a1a9ac556d01e1b0df6fe64e67cb646fa4118. Noticed by inspection.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
`RUST_OPTIONAL` is set so that ebuilds must explicitly consume
Rust features.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Inherit the rust eclass and take advantage of eclass features like
`RUST_MIN_VER`.
`RUST_DEPEND` was moved into the rust eclass in the previous commit
and is now prowided via this mechanism
`CARGO_OPTIONAL` now sets `RUST_OPTIONAL`, requiring ebuilds to
set `RUST_DEPEND` manually and manage both cargo and rust eclass
functions.
Replace calls to `cargo` with the rust eclass exported ${CARGO}.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The rust eclass acts similarly to the llvm eclass.
It works with optional `RUST_{MAX,MIN}_SLOT` variables to
enable ebuilds to trivially dependencies on appropriate
Rust SLOTs.
A `RUST_NEEDS_LLVM` variable can be set to have the eclass read
`LLVM_COMPAT` and generate an llvm-r1-USE-gated dependency string.
`RUST_USEDEP`, if set will be included in the dependency string
and checks against installed packages.
In either case these are stored in `RUST_DEPEND` for consumpion
in the ebuild, and added to BDEPEND unless unless `RUST_OPTIONAL`
is set. `RUST_DEPEND` will only ever include in-tree slots; there
is no need to set `RUST_MIN_VER` if all in-tree versions are suitable.
If `RUST_MIN_VER` is set to a value older than the oldest in-tree slot
it is treated as if it is set to the lowest available.
The default `rust_pkg_setup` will prefix the selected slot to
`PATH` and export `RUSTC` and `CARGO` variables pointing to that
slot for ease-of-use.
This should prevent issues like:
Bug: https://bugs.gentoo.org/907492
Bug: https://bugs.gentoo.org/942444
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
| |
Fixes: d82f81cd65b9a668bd7940151e3fa876d4b0ce92
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/268313
Bug: https://bugs.gentoo.org/318625
Bug: https://bugs.gentoo.org/539958
Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>
Closes: https://github.com/gentoo/gentoo/pull/39180
Signed-off-by: Florian Schmaus <flow@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>
Signed-off-by: Florian Schmaus <flow@gentoo.org>
|
|
|
|
|
|
|
|
| |
We want to recover logs from that too.
Bug: https://bugs.gentoo.org/942769
Fixes: 5bed0c77a1c54ac9297db4bb54af2e45c0558ec7
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Acked-by: Sam James <sam@gentoo.org>
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
| |
Same as 72d5ea56d41b7d5aac351854b7479f5c2c430c83, the flag got renamed.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
| |
Removes java-pkg_set-current-vm
Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>
Closes: https://github.com/gentoo/gentoo/pull/38836
Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org>
|
|
|
|
|
|
| |
Bug: https://gcc.gnu.org/PR116975
Closes: https://bugs.gentoo.org/940750
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
| |
This will replace "edotnet fsi" as used in "app-shells/pwsh" package.
Signed-off-by: Maciej Barć <xgqt@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Speeds up "dotnet restore". Especially can be noticed when running
without network sandbox.
Suggested by vimproved on IRC - thanks!
See also: https://github.com/NuGet/Home/issues/13062
Signed-off-by: Maciej Barć <xgqt@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
| |
This is an experimental flag not yet merged upstream but filtering
it makes it easier to test with so it doesn't confuse older unpatched (locally)
GCCs.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A user on the forums reported a build failure with:
`-march=znver4 -mavx512vp2intersect`
On its own, there is no issue there (expanded from -march=native) but
when Qt passes `-march=haswell` to build certain parts (e.g. avx2 bits
for runtime detection regardless of what CHOST supports), it overrides
znver4 and keeps -mavx512vp2intersect resulting in an incomplete set
and then qsimd_p.h complains
Do not plan to pursue this myself, but this specific issue could
be improved upstream by passing -mavx2 and others rather than
-march=haswell (this would also allow overriding a -mno-avx2 that
we currently need to change), and/or ideally by making qsimd_p.h
be able to deal with these configurations without #error.
If problems keep piling up, could consider always filtering *all*
-m{,no-}<instr> flags and doing x86-64-v* unconditionally. Albeit
that'd still require maintaining a list of these not to filter
unrelated -m* flags which could be important.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|