Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
... /builddir/build/BUILD/nfs-ganesha-2.4.2/src/NodeList/nodelist_range.c: In function 'nl_rangelist_add_list': /builddir/build/BUILD/nfs-ganesha-2.4.2/src/NodeList/nodelist_range.c:333:13: error: comparison between pointer and zero character constant [-Werror=pointer-compare] while (end != '\0' && end < in_list + in_list_size + 1) { ^~ /builddir/build/BUILD/nfs-ganesha-2.4.2/src/NodeList/nodelist_range.c:333:9: note: did you mean to dereference the pointer? while (end != '\0' && end < in_list + in_list_size + 1) { ^ cc1: all warnings being treated as errors make[2]: Leaving directory '/builddir/build/BUILD/nfs-ganesha-2.4.2/src' ...
ignore Comment 1. ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/glusterfs.spec'], logger=<mockbuild.trace_decorator.getLog object at 0x7f2b8d648390>uid=1000user='mockbuild'chrootPath='/var/lib/mock/f26-build-7471289-689477/root'shell=FalseprintOutput=Falsetimeout=172800gid=425env={'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'TERM': 'vt100', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8'}) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/glusterfs.spec'] with env {'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'TERM': 'vt100', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8'} and shell False sh: /usr/bin/python: No such file or directory sh: /usr/bin/python: No such file or directory Building target platforms: x86_64
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.