Bug 1439233

Summary: rebuild of i2c-tools rpm fails with error: 'dev_path' undeclared
Product: Red Hat Enterprise Linux 7 Reporter: Rachel Sibley <rasibley>
Component: i2c-toolsAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED ERRATA QA Contact: Rachel Sibley <rasibley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: thozza, zdohnal
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: i2c-tools-3.1.0-13.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 19:53:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rachel Sibley 2017-04-05 13:24:37 UTC
Description of problem:
During the rpmbuild --rebuild step from TPS errata for i2c-tools component, the command failed
with the following errors

Version-Release number of selected component (if applicable):
i2c-tools-3.1.0-12.el7

How reproducible:
Always

Steps to Reproduce:
1. rpmbuild --rebuild --define "dist .el7" --target=x86_64 --rcfile /tmp/tps_rpmrc_phBHsd:/usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc i2c-tools-3.1.0-12.el7.src.rpm

2.
3.

Actual results:
FAILED to rebuild i2c-tools-3.1.0-12.el7.src.rpm -- return code 256
 REBUILD: FAIL for i2c-tools-3.1.0-12.el7.src.rpm
 BUILDLOG: i2c-tools-3.1.0-12.el7.src.rpm-x86_64-rebuild.log contains full details.  Reports from make and rpmbuild, with line numbers:
 46-tools/i2cbusses.c: In function 'try_load_i2c_dev_mod':
 47-tools/i2cbusses.c:203:7: error: 'dev_path' undeclared (first use in this function)
 48-  free(dev_path);
 49-       ^
 50-tools/i2cbusses.c:203:7: note: each undeclared identifier is reported only once for each function it appears in
 51:make: *** [tools/i2cbusses.o] Error 1
 52:error: Bad exit status from /var/tmp/rpm-tmp.JF1z8w (%build)
 53-
 54-
 55-RPM build errors:
 56-    Bad exit status from /var/tmp/rpm-tmp.JF1z8w (%build)
 Last 20 lines of Build Log:
 patching file tools/Module.mk
 + exit 0
 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.JF1z8w
 + umask 022
 + cd /home/test/rpmbuild/BUILD
 + cd i2c-tools-3.1.0
 + make 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic'
 cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wundef -Wmissing-prototypes -Iinclude   -DUSE_LIBKMOD -c tools/i2cdetect.c -o tools/i2cdetect.o
 cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wundef -Wmissing-prototypes -Iinclude   -DUSE_LIBKMOD -c tools/i2cbusses.c -o tools/i2cbusses.o
 tools/i2cbusses.c: In function 'try_load_i2c_dev_mod':
 tools/i2cbusses.c:203:7: error: 'dev_path' undeclared (first use in this function)
 free(dev_path);
 ^
 tools/i2cbusses.c:203:7: note: each undeclared identifier is reported only once for each function it appears in
 make: *** [tools/i2cbusses.o] Error 1
 error: Bad exit status from /var/tmp/rpm-tmp.JF1z8w (%build)
 RPM build errors:
 Bad exit status from /var/tmp/rpm-tmp.JF1z8w (%build) 

Expected results:
RPM rebuilds successfully

Additional info:

Comment 5 Rachel Sibley 2017-04-11 15:58:48 UTC
Moving to verified state as the rpmbuild --rebuild step is passing now with the latest rpm i2c-tools-3.1.0-13.el7.src.rpm

Comment 6 errata-xmlrpc 2017-08-01 19:53:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2244