Bug 1884951

Summary:	clangllvm plugin is installed in wrong directory on i686
Product:	[Fedora] Fedora	Reporter:	Elliott Sales de Andrade <quantum.analyst>
Component:	annobin	Assignee:	Nick Clifton <nickc>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	34	CC:	fweimer, jakub, nickc
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	annobin-9.35-2.fc34	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-08 06:30:31 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 Elliott Sales de Andrade 2020-10-03 21:18:13 UTC

On i686, the annobin clang plugin is installed here:
# rpm -ql annobin| grep clang
/usr/lib64/clang/11.0.0/lib
/usr/lib64/clang/11.0.0/lib/annobin-for-clang.so
/usr/lib64/clang/11.0.0/lib/annobin-for-llvm.so

However, on i686, clang installs its files in /usr/lib/clang/.


Version-Release number of selected component (if applicable):
annobin-9.35-1.fc34.i686


Steps to Reproduce:
1. mock -r fedora-rawhide-i386 --install clang
2. mock -r fedora-rawhide-i386 --shell
3. ls /usr/lib*/clang/*


Actual results:
As noted above, the plugin is in /usr/lib64. These are also 32-bit executables:

$ file /usr/lib64/clang/11.0.0/lib/annobin-for-*
/usr/lib64/clang/11.0.0/lib/annobin-for-clang.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=f7357bdbcdead8a9fad3d016b6240e62a64ae4e6, stripped
/usr/lib64/clang/11.0.0/lib/annobin-for-llvm.so:  ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=5e5fd59f77734dd8d7a75401839fc9415fde1ff4, stripped


Expected results:
I don't know exactly where clang/llvm look for plugins, but 32-bit libraries should be in /usr/lib, not /usr/lib64.

Comment 1 Elliott Sales de Andrade 2020-10-03 21:27:01 UTC

I don't think clang searches there, even:

$ clang -print-search-dirs
programs: =/usr/bin:/usr/lib/gcc/i686-redhat-linux/10/../../../../i686-redhat-linux/bin
libraries: =/usr/lib/clang/11.0.0:/usr/lib/gcc/i686-redhat-linux/10:/usr/lib/gcc/i686-redhat-linux/10/../../..:/usr/bin/../lib:/lib:/usr/lib

Comment 2 Nick Clifton 2020-10-05 11:56:11 UTC

Hi Elliot,

  Thanks for reporting this problem.  I have now updated the annobin.spec file to extract the first directory listed after "libraries" in the output from 'clang --print-search-dirs'.  I hope that this will prove to be the correct location...

  By the way, does this mean that you are (trying to) using the annobin plugin with clang ?  If so, I would love to hear about how it is going.

Cheers
  Nick

Fixed in: annobin-9.35-2.fc34

Comment 3 Elliott Sales de Andrade 2020-10-08 08:27:35 UTC

No sorry, I just have something that checks /usr/lib64/clang/ and /usr/lib/clang/, which was confused by the lib64 directory existing.

PS, I think this also affects F33 as well.

Comment 4 Nick Clifton 2020-10-08 11:53:02 UTC

(In reply to Elliott Sales de Andrade from comment #3)
> No sorry, I just have something that checks /usr/lib64/clang/ and
> /usr/lib/clang/, which was confused by the lib64 directory existing.

Ah - that makes sense.

> PS, I think this also affects F33 as well.

Yes and no.  Yes the bug is in the annobin.spec file for F33.  But the Clang and LLVM plugins are not built or installed for F33.  Well not unless you build with "--with clangplugin --with llvmplugin", so it is unlikely that anyone will come across the problem.  (I have started enabling the plugins by default in rawhide as an experiment to see if there are problems).

Comment 5 Ben Cotton 2021-02-09 15:19:41 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 6 Ben Cotton 2022-05-12 16:57:46 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Ben Cotton 2022-06-08 06:30:31 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.