<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">I did reply to another thread on the
same subject.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">In short ...</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The only way to make this work is to
place the kernel and out-of-tree kernel modules into a layer of
their own.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><span style="font-size: 16px;">Scott</span></div>
<div class="moz-cite-prefix"><span style="font-size: 16px;"><br>
</span></div>
<div class="moz-cite-prefix"><span style="font-size: 16px;"><br>
</span></div>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2020-03-02 10:41 a.m., Saul Wold
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5d549501-7ae7-5ab2-91b9-fce6c184e737@linux.intel.com">
<br>
Scott, Don:
<br>
<br>
Not sure if you saw this email? Can you guys take a look and
comment on if there is a solution to providing 2 different GCC
versions?
<br>
<br>
Thanks
<br>
Sau!
<br>
<br>
<br>
<br>
-------- Forwarded Message --------
<br>
Subject: Re: [Starlingx-discuss] MoM: Weekly StarlingX
non-OpenStack distro meeting, 2/12/2020
<br>
Date: Thu, 13 Feb 2020 12:04:48 +0000
<br>
From: Lin, Shuicheng <a class="moz-txt-link-rfc2396E" href="mailto:shuicheng.lin@intel.com"><shuicheng.lin@intel.com></a>
<br>
To: Sun, Austin <a class="moz-txt-link-rfc2396E" href="mailto:austin.sun@intel.com"><austin.sun@intel.com></a>,
'<a class="moz-txt-link-abbreviated" href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>'
<a class="moz-txt-link-rfc2396E" href="mailto:starlingx-discuss@lists.starlingx.io"><starlingx-discuss@lists.starlingx.io></a>
<br>
<br>
Hi BUILD team and all,
<br>
In yesterday's meeting, we prefer to build CentOS 8 kernel with
gcc-8.2.1, while keep other packages with gcc-4.8.5.
<br>
But current build system doesn't support gcc switch during package
build.
<br>
First, gcc is a base package defined in mock config, and gcc with
latest version(8.2.1) will be auto installed to mock environment
when mock init, before any package building.
<br>
This will lead to all packages build with gcc-8.2.1.
<br>
Another problem is, mock environment is reused for all packages
build. There is no mock environment clean between packages build.
To support different packages with different gcc, we need have two
mock environment with different gcc version, and accept build for
corresponding packages build only.
<br>
It will be a big change for current build system.
<br>
Do you know how could we handle the case better?
<br>
<br>
Base on upper problem, I prefer to go with option 2, gcc-4.8.5 for
CentOS 8 kernel and other CentOS 7 packages.
<br>
GCC upgrade will be done later along with CentOS 8 base OS
packages upgrade. Please share me your suggestion.
<br>
Thanks.
<br>
<br>
Best Regards
<br>
Shuicheng
<br>
<br>
-----Original Message-----
<br>
From: Sun, Austin <a class="moz-txt-link-rfc2396E" href="mailto:austin.sun@intel.com"><austin.sun@intel.com></a> Sent: Wednesday,
February 12, 2020 11:08 PM
<br>
To: '<a class="moz-txt-link-abbreviated" href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>'
<a class="moz-txt-link-rfc2396E" href="mailto:starlingx-discuss@lists.starlingx.io"><starlingx-discuss@lists.starlingx.io></a>
<br>
Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack
distro meeting, 2/12/2020
<br>
<br>
Hi All:
<br>
Thanks join the call. MoM for 2/12 meeting:
<br>
- Ceph containerization status and comments address (Martin)
<br>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007731.html">http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007731.html</a>
<br>
[1] rook is integrating into application-app currently ,
if use remove/delete platform-application, ceph-cluster will be
destory. this is admin choose if they want to do it. [2]
only will consolated app (sysinv or rook) to controller ceph to
discuss further in maillist. - Pbr update (
JITStack-Wesley)
<br>
build-time issue address
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007676.html">http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007676.html</a>
, Wesley will update result by End of Week to maillist.
reply the email and do an exmplaination - CentOS8 update (
Austin/Shuicheng) Strategy discuss 1) kernel
4.18 uprade only , which new gcc 8.2 is using new gcc will cause
compile el7 rpms failure. 2) use old gcc(4.x) to
compile new kernel + master rpms 3) mixing gcc
using (kernel will use new gcc , and other use old gcc) , --
prefer this way , but current mock does not support 2 gcc
co-worker. work item update kernel-rt. use
kernel 4.18.x.147 , std and rt which is using centos8.1, as much
as using current rpm. kubeadm (kube-proxy) issue update.
keep legacy mode binary in iptables. drbd8 --- fix compile
issues, and worked. puppet 4.8 w/ ruby 2.5 --worked , send
result python2/python3 bring python3 to master , and start
python2to3 converting for example nfv. Opens - Vista Creek
(FPGA card) support still need confirm i40e
drivers New OPEA driver will be released by end of this
week. SRIOV device plugin
<a class="moz-txt-link-freetext" href="https://github.com/intel/sriov-network-device-plugin/pull/196">https://github.com/intel/sriov-network-device-plugin/pull/196</a>
<br>
-Open
<br>
<br>
Thanks.
<br>
BR
<br>
Austin Sun. _______________________________________________
<br>
Starlingx-discuss mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
<br>
_______________________________________________
<br>
Starlingx-discuss mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>