<div dir="ltr"><div dir="ltr">Thank you for the info!<div>Where do you get the config file for kernel rebuild(
<span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">This one: ~/rpmbuild/SOURCES/config-4.14.13-x86_64</span>
)? </div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 29, 2018 at 3:14 PM, Phil Perry <span dir="ltr"><<a href="mailto:phil@elrepo.org" target="_blank">phil@elrepo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 29/08/18 20:46, Alan Bartlett wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 29 August 2018 at 02:08, Andrew Gurinovich <<a href="mailto:altmind@gmail.com" target="_blank">altmind@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello.<br>
I would like to rebuild the whole elrepo with custom compiler flags for<br>
personal use.<br>
Can you please suggest, how the rpms are being build right now?<br>
</blockquote>
<br>
I can only speak for the kernel (kernel-lt & kernel-ml) build process.<br>
Mock is used to provide a clean, controlled, chroot environment for<br>
the native OS. That is RHEL6 and RHEL7.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I'm trying to rpmbuild from spec files, there are no sources in<br>
/home/user/rpmbuild<br>
When I'm trying to build kernel-ml, there is no config file.<br>
</blockquote>
<br>
Install the .nosrc.rpm package into your private rpmbuild directory<br>
structure and drop the relevant linux-4.X.Y.tar.xz file (obtained from<br>
upstream, <a href="http://kernel.org" rel="noreferrer" target="_blank">kernel.org</a>) into you SOURCES/ directory.<br>
<br>
Alan.<br>
</blockquote>
<br></span>
The rest of the repo is built likewise, in mock.<br>
<br>
All kmod .src.rpms should rebuild cleanly against the latest RHEL kernel. There are some exceptions, notably .nosrc.rpms which do not contain the upstream tarball to save space/bandwidth. As Alan mentioned above, for any .nosrc.rpms you will need to fetch the upstream source tarball in addition to the .nosrc.rpm, which should always be linked towards the start of the SPEC file.<br>
<br>
Generally, kmod packages do not _need_ to be built in mock as typically they do not link anything other than the kernel they are built against; anything else should always be built in mock for consistency.<br>
<br>
Rebuilding kmod packages will result in kernel modules which are not signed by elrepo for Secure Boot. If you are using Secure Boot you will probably want to sign the modules with your own signing key. There is logic in the SPEC file to allow for this from the command line at build time. If doing this in mock, you will need to install your signing keys into your build root before building.<br>
<br>
The VirtualGL-libs i686 package on el7 has hints in the SPEC file how to build as there is no 32-bit rhel7 tree to build against in mock.<br>
<br>
Hope that helps.<span class="HOEnZb"><font color="#888888"><br>
<br>
Phil</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
elrepo mailing list<br>
<a href="mailto:elrepo@lists.elrepo.org" target="_blank">elrepo@lists.elrepo.org</a><br>
<a href="http://lists.elrepo.org/mailman/listinfo/elrepo" rel="noreferrer" target="_blank">http://lists.elrepo.org/mailma<wbr>n/listinfo/elrepo</a><br>
</div></div></blockquote></div><br></div>