[LU-9948] rpmbuild failure with gcc 6.3. ERROR: No build ID note found in /usr/bin/lfs Created: 05/Sep/17 Updated: 27/Jan/23 Resolved: 27/Jan/23 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Chris Horn | Assignee: | WC Triage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
Got an rpmbuild error when using gcc 6.3.0. [build@localhost lustre-release]$ gcc --version
gcc (GCC) 6.3.0
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[build@localhost lustre-release]$ git describe HEAD
v2_10_52_0-75-ge1679d0
[build@localhost lustre-release]$ sh ./autogen.sh ; ./configure --disable-server --enable-client --disable-checksum --disable-doc --with-o2ib=yes --with-linux=/usr/src/kernels/3.10.0-514.16.1.el7.x86_64/ --disable-dlc ; make -j 16 rpms
<snip>
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /tmp/rpmbuild-lustre-build-zMFdDRfM/BUILD/lustre-2.10.52_75_ge1679d0
extracting debug info from /tmp/rpmbuild-lustre-build-zMFdDRfM/BUILDROOT/lustre-2.10.52_75_ge1679d0-1.x86_64/usr/bin/lfs
*** ERROR: No build ID note found in /tmp/rpmbuild-lustre-build-zMFdDRfM/BUILDROOT/lustre-2.10.52_75_ge1679d0-1.x86_64/usr/bin/lfs
error: Bad exit status from /tmp/rpmbuild-lustre-build-zMFdDRfM/TMP/rpm-tmp.MVkgeX (%install)
RPM build errors:
Bad exit status from /tmp/rpmbuild-lustre-build-zMFdDRfM/TMP/rpm-tmp.MVkgeX (%install)
make: *** [rpms] Error 1
After some googling I found that adding 'export LDFLAGS="$LDFLAGS -Wl,--build-id"' to the lustre.spec file resolved the issue. However, I'm not sure the best way to set this in Lustre's build system. Some guidance would be appreciated. |
| Comments |
| Comment by Chris Horn [ 27/Jan/23 ] |
|
close old minor bug that has probably been fixed along the way |