> The right thing to do with an incompatible OpenMP is to silently disable
> OpenMP unless explicitly requested by --enable-openmp. Whether it's worth the
> trouble is a separate question, writing configure.ac logic is ... yeah. No
> cute kittens will be harmed if we set the default to "yes"
- simplify code / fix build failure with -fsanitize=address
- dont call exit() from middle of librpmbuild
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1353
-- Commit Summary --
* Simplify logic to work around gcc
Also, `rpm.with("foo")` and `rpm.without("foo")` would be lovely.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Merged #1353 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1353#event-3713750258___
Rpm-maint mailing list
@pmatilai Coming back to this PR after a while, I wonder if silently disabling
OpenMP (if the required version isn't available) is really what we want.
Wouldn't it be better to just fail and let the user disable OpenMP explicitly
with `--disable-openmp` if he/she decides so?
--
You are
Optimally, ./configure without specific arguments is supposed to just figure
out a configuration that will work on this system, and only error out if it
cannot do that - or is explicitly requested to do incompatible things.
The right thing to do is to silently disable OpenMP unless explicitly
I was thinking how to handle this today. I've only figured out *wrong*
solutions:
1. Modify `%__global_provides_exclude_from` to include
`%{_libdir}/python\d+\.\d+/.+\.so`.
This obviously has several problems: I cannot really do it from Python macros,
so the information would need to be kept
Edit: commit message updated to talk about _minimize_writes instead of
_minimize_io. And here I was wondering why I can't seem to reproduce it now...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@pmatilai pushed 1 commit.
f22f7cc156822d6ffae77ad5101150f2514a5e9f Upgrade FA_TOUCH to FA_CREATE if the
file went away (RhBug:1872141)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
- Fix possible read beyond buffer in rstrnlenhash()
- Add missing terminator to copyTagsFromMainDebug array
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1354
-- Commit Summary --
* Add missing terminator to
@pmatilai Updated, please review.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1325#issuecomment-684947396___
Rpm-maint
@dmnks pushed 2 commits.
82c5af992ed87bb6665de2d382166a563cc7b398 Check for OpenMP version at configure
time
c3af4801917c6cf3d5b5153a02f4cc09f98d6ca2 Bump Lua to 5.2 in configure script
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
12 matches
Mail list logo
