On Sun, Mar 18, 2018 at 5:58 PM, Baho Utot <baho-u...@columbus.rr.com> wrote: > > > On 3/18/2018 10:25 AM, Neal Gompa wrote: >> >> On Sun, Mar 18, 2018 at 10:20 AM, Baho Utot <baho-u...@columbus.rr.com> >> wrote: >>> >>> I am building a scratch built linux system and I am using rpm as the >>> package >>> manager. >>> >>> I want to disable build-id in rpm so it discards or doesn't act on the >>> build-id. >>> >>> Can build-id processing be disabled in a macro file? >>> >>> If so how does one do that. >>> >>> Want to remove the following from the binary rpm package >>> >> >> If you want debuginfo without the build-id files in the main rpm, set >> the following in your rpm vendor macros file: >> >> %_build_id_links alldebug >> >> I also highly recommend you set these two in your vendor config, as it >> makes your debuginfo subpackages more focused: >> >> %_debugsource_packages 1 >> %_debuginfo_subpackages 1 >> >> > > I just want to throw away the build-id as I don't have debug packages nor am > I using sub-packages. This is just a project to build LFS and inserting rpm > as a package manager as LFS does not have a package manager. I just need to > kill off the build-id files in the binary rpm package as the installation > fails because /usr/lib/buil-id doe not exist. Having build-id files has no > use on my scratch built systems. > That is why I want to just kill them off. > > I get the build-id issue when I am using arch linux as the host. > If I use a scratch built linux for the host build-id does not show up in the > first build of a package but it does show up if I rebuild the package. > >
By default, rpm will not produce debuginfo packages (unless you install the macros.debug file in the source tree). But if you want to kill off build-id links, put the following in your vendor macros file: %_build_id_links none -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ Rpm-ecosystem mailing list Rpm-ecosystem@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-ecosystem
