The system GNU C Compiler
This package is based on the package 'gcc' from project 'openSUSE:Factory'.
The system GNU C Compiler.
- Devel package for openSUSE:Factory
-
10
derived packages
- Links to openSUSE:Factory / gcc
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:gcc/gcc && cd $_ - Create Badge
Refresh
Refresh
Source Files (show merged sources derived from linked package)
| Filename | Size | Changed |
|---|---|---|
| _link | 0000000138 138 Bytes | |
| _multibuild | 0000000051 51 Bytes | |
| cpp | 0000000082 82 Bytes | |
| gcc.changes | 0000018239 17.8 KB | |
| gcc.spec | 0000027081 26.4 KB |
Comments 10
This comment has been deleted
https://bugzilla.opensuse.org/show_bug.cgi?id=1090209
GCC 10.1 released [2020-05-07] https://gcc.gnu.org/gcc-10/
Could you add provides of the type "gcc-c++ = %{version}" to allow usage like Requires gcc-c++ >= 9. Currently you need repository specific workarounds to reach the same goal.
Such provides would conflict with the real gcc-c++ package, a gcc9 package also doesn't provide g++, it provides g++-9 so not sure how such provides helps the problem you have (which I can only anticipate).
See https://build.opensuse.org/request/show/910100
Exactly, and you'd still need to spell out that -DCMAKE_CXX_COMPILER="%{_bindir}/g++-9" so you win nothing (IMHO).
Why is /etc/alternatives.d not used like for other similar packages like java?
Essentially the problem to resolve is to request a gcc-c++ version higher than a given version without needing to request a specific package name. That happens when the gcc-c++ package targets an older version, but the newer one is already existing.
You want gcc-c++ for all the systems which already use your minimum version, but for the older OS you need gccX-c++, so you get the minimum you need. But if you required gccX-c++ always then you get an OLD or not existing compiler on the newer systems, which is not wanted.
If gcc-c++ conflicts, what about a new provides like "gcc-c++-compiler = %{version}"?
This has been discussed to death. OBS package comments are not really the correct forum to repeat that. You can use bugzilla or the mailing list if you like.