Bug ID | 1177140 |
---|---|
Summary | openssh ppc64 build failure undefined reference to `sshsk_sign' |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | PowerPC |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Other |
Assignee | screening-team-bugs@suse.de |
Reporter | normand@linux.vnet.ibm.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Created attachment 842120 [details] openssh_standard_ppc64_202009291700.log.gz openssh ppc64 build failure undefined reference to `sshsk_sign' as reported on OBS https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/openssh (no failure for ppc64le) attached openssh_standard_ppc64_202009291700.log.gz extract: === [ 120s] /usr/lib64/gcc/powerpc64-suse-linux/10/../../../../powerpc64-suse-linux/bin/ld: ./libssh.a(sshkey.o): in function `sshkey_sign': [ 120s] /home/abuild/rpmbuild/BUILD/openssh-8.3p1/sshkey.c:2799: undefined reference to `sshsk_sign' [ 120s] collect2: error: ld returned 1 exit status === If I compare with log of ppc64le that passed, I identified following compilation options present in ppc64le but not ppc64: === -fmessage-length=0 -grecord-gcc-switches -flto=auto === I assume that no packages are build with LTO for ppc64. If I force -flto=auto for ppc64 specifically for this package then the build complete as per https://build.opensuse.org/package/view_file/home:michel_mno:branches:network/openssh/openssh.changes?expand=1 BUT I am not sure this is the right thing to be done.