Hi guys.
Is possible to cheat or hack /mock /somehow - I get that each package specs tells the 'what dependencies are needed' story - to build env would use different compiler and tools needed for compilations? Or perhaps tool different than /mock/ is meant for that, is such exists?
many thanks, L.
You can either change the dependencies in SRPM or install additional toolchain into mock. But if you provided more context, it could be probably easier spot what is your struggle.
Vít
Dne 07. 11. 25 v 8:42 lejeczek via buildsys napsal(a):
Hi guys.
Is possible to cheat or hack /mock /somehow - I get that each package specs tells the 'what dependencies are needed' story - to build env would use different compiler and tools needed for compilations? Or perhaps tool different than /mock/ is meant for that, is such exists?
many thanks, L.
I'm thinking of scenarios - certainly not original thoughts - where a newer compilers set would be very advantageous to use, sometimes a must-have thing perhaps. An example: best would be, the easiest I'd hope, to make - in cases of Centos(& rhel family?) - use, if possible,of gcc-toolset.
Getting new gcc with/via .spec would mean building - firstly - such a newer version(s) of gcc into a private repo & then using '--addrepo', but... those compilations of newer gcc usually/always fail - my past experience tells me & if memory does not fail.
Again, simply, taking advantage of new gcc releases which come - as opposed to say, oldish c9's ver 11 - with much better hw target optimizations. And again - since it's not original nor unique thought - people must be doing it already, somehow... with mock?
many thanks, L.
buildsys@lists.fedoraproject.org