The distro-wide architecture set in CFLAGS is overriden by 389-ds-base buildsystem. It tries to set -march to non-existing values on s390(x), for ppc* such compiler option doesn't even exist. The buildsystem should touch the -march options at all. See also https://fedoraproject.org/wiki/Packaging:Guidelines#Compiler_flags from build logs http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1851358 ... gcc -Wall -Wno-unknown-pragmas -std=c99 -march=s390 -c -I"src" -I"inc" -fpic -O0 -g -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m31 -march=z9-109 -mtune=z10 -o obj/queue_queue.o src/queue/queue_queue.c gcc: error: unrecognized argument in option '-march=s390' gcc: note: valid arguments to '-march=' are: g5 g6 z10 z196 z9-109 z9-ec z900 z990 zEC12 ... and http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2559662 ... gcc -Wall -Wno-unknown-pragmas -std=c99 -march=ppc64le -c -I"src" -I"inc" -fpic -O0 -g -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mcpu=power7 -mtune=power8 -o obj/queue_new.o src/queue/queue_new.c gcc -MM -std=c99 -I"src" -I"inc" src/stack/stack_delete.c >obj/stack_delete.d cc1: error: unrecognized command line option '-march=ppc64le' ... Version-Release number of selected component (if applicable): 389-ds-base-1.3.4.0-1.fc22
Fixed for the version and newer: 389-ds-base-1.3.4.1-1.fc22
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.4.1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1533
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.