On Dienstag, 3. April 2018 11:34:02 Andreas Schwab wrote:
On Mär 31 2018, Hans-Peter Jansen <hpj@urpla.net> wrote:
In a local OBS, where I attempt to build Kernel:stable and friends, I fiddled with below to get $subject going, but failed so far, barfing on a missing gcc.
Looks, like I need to create a gcc7-default package, that symlinks gcc7 and consorts to gcc. Has anybody done this before?
Guess, this plan isn't that uncommon nowadays...
%define gcc_version 7 Ignore: libgcc_s1 Preinstall: !libgcc_s1 libgcc_s1-gcc7 Prefer: -libstdc++6 libstdc++6-gcc7 Prefer: -libtsan0 libtsan0-gcc7 Prefer: -libgomp1 libgomp1-gcc7 Prefer: -libgcc_s1 libgcc_s1-gcc7 Prefer: -libatomic1 libatomic1-gcc7 Prefer: -libcilkrts5 libcilkrts5-gcc7 Prefer: -libitm1 libitm1-gcc7 Prefer: -liblsan0 liblsan0-gcc7 Prefer: -libmpx2 libmpx2-gcc7 Prefer: -libubsan0 libubsan0-gcc7
That's all you should need, together with a branch of the gcc package with has gcc_version and gcc_suffix adjusted.
Well, I find it a bit expensive to rebuild two gcc packages (in worst case) just for changing the compiler, but possibly the way to go. Does anybody know, how the build system behaves, if I "overload" %___build_pre of /usr/lib/rpm/macros within another macro file? Is the load order of macro files documented/deterministic? Would be much easier to Preinstall a rpm_macros_gcc7 package, where a matching CC is exported in %___build_pre, wouldn't it? Cheers, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org