> On Wed, 19 Aug 2020 09:25:22 +0200, Panu Matilainen wrote: We can't really
> require both gcc and clang for rpm compilation,
> I do not understand why but OK.
Should be pretty obvious really, starting with: it's a bit much to ask people
to (possibly build and) install a whole another compiler just for a few
test-cases that might not even concern them.
> Do you plan to update the .spec BuildRequires?
What spec? There's no spec in rpm upstream, what individual distros do about
this is up to them.
> we need to skip (instead of failing) debugedit tests that depend on a
> non-present compiler
> done
> This is equally true for both gcc and clang, perhaps it could be centrally
> handled in RPM_DEBUGEDIT_SETUP.
> Done only for clang. (1) gcc testing is outside of the scope of my patchset.
Thanks. I agree gcc testing is not in your scope really, but wouldn't the same
thing handle testing gcc just as easily?
(2) I do not think there can exist a system without gcc - in such case gcc is a
symlink to clang. lrwxrwxrwx 1 u0_a184 u0_a184 8 Aug 6 09:31
/data/data/com.termux/files/usr/bin/gcc -> clang-10* Jan
Um, I don't think this link is any universal setup. And there are other
compilers besides gcc and clang. Rpm requires a C99 compiler, if there are
compiler-specific requirements that's a bug (there probably are some)
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1332#issuecomment-676004730
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
