Hi Vasily, I should have been more clear about the circumstances and that I don't actually experience problems because of the gcc version used in the kernel-RPMs you provide. I made the inquiry because while upgrading DRBD to the latest stable version, I stumbled across a note in the DRBD manual that states, one should make sure to use the same gcc version for compiling the module as has been used for compiling the kernel. [1]
I now have been contemplating one of the following * keep on ignoring Linbit's advice of using the same gcc version * compiling the kernel with gcc provided by CentOS/RedHat (4.4.7 20120313) * compiling the module with your version of gcc (4.4.6 20120305) Currently I ignore Linbit's advice but as I reckon they have a reason for their recommendation I was exploring option three but I couldn't find a distro that ships your version of gcc as standard - maybe you could point me to one. Of course the fourth option, you "upgrading" your gcc to the same version used by RedHat would be the most convenient for me (and everybody else concerned about such recommendations by kernel-module authors). But I guess you also have your reasons why you use a version of gcc that is not shiped with the distro the kernel is supposed to be used with :) Thanks for all the really great work! Joseph [1] http://drbd.linbit.com/users-guide/s-build-from-source.html Am 18.05.2015 um 11:08 schrieb Vasily Averin: > Dear Joseph, > could you please explain the problem in more details? > > In fact in Parallels Cloud Server we regularly build some modules > right on the node by using gcc version installed on host. > It really differs from gcc version used for kernel compilation, > but it does not lead to any troubles. > I have such mismatch on my test node and did not noticed > any warning/errors during recompilation of various kernel modules. > > Frankly speaking I remember some such problems, > but it was happen long time ago I now I cannot remember > neither reason nor solution. > > I've googled such messages, but found only claim on NVIDIA installer, > with workaround "--no-cc-version-check" > > Thank you, > Vasily Averin > > On 14.04.2015 19:33, Joseph wrote: >> Hi OpenVZ Team, >> >> is there a special reason why you use a different gcc Version for the >> kernels you provide >> cat /proc/version >> Linux version 2.6.32-042stab106.4 (root@kbuild-rh6-x64) (gcc version >> 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Mar 27 15:19:28 MSK 2015 >> that either CentOS6 or RHEL6 ship with: >> gcc -v >> gcc-Version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) >> >> I've need a kernel modules that states it should be compiled with the >> same exact gcc version like the kernel running. Should I set up a >> Fedora19 vbox to compile my module or can you maybe suggest >> faster/easier way that's deemed safe? >> >> Thanks, >> Joseph >> >> >> _______________________________________________ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
