Bug 14504

Summary:	qemuriscv eudev text relocation warning
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Jon Mason <jon.mason>
Component:	virtual machines	Assignee:	Maxin B. John <maxin.john>
Status:	RESOLVED OBSOLETE	QA Contact:
Severity:	minor
Priority:	Medium	CC:	maxin.john, raj.khem, randy.macleod
Version:	3.4
Target Milestone:	5.3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Jon Mason 2021-08-10 20:06:01 UTC

When compiling core-image-base on either of the qemuriscv32 or qemuriscv64 machines, I see the following warning:

WARNING: eudev-3.2.10-r0 do_package_qa: QA Issue: eudev: ELF binary /usr/bin/udevadm has relocations in .text
eudev: ELF binary /usr/libexec/udevadm has relocations in .text [textrel]

I am unsure if this is a regression or a new problem, as I have not tried this before.  Both machines complete compiling and pass testimage.  So, it is not  significant problem, but they are the only qemu machines with warnings.

Comment 1 Randy MacLeod 2021-08-12 14:38:29 UTC

Khem, Ross thought you'd want to be CCed here.

Comment 2 Khem Raj 2021-08-12 17:03:33 UTC

yes thanks, these are known issues though, something to do with PIE implementation in binutils. There is a bunch of ignores I have for this error in meta-riscv

Comment 3 Randy MacLeod 2023-10-30 15:37:24 UTC

Build move to 5.0 -- ../Randy

Comment 4 Randy MacLeod 2024-04-25 01:13:51 UTC

Bulk move of 5.0 medium importance issues to 5.99.
Move to 5.1 if you want to actively work on an issue.

Comment 5 Randy MacLeod 2024-04-25 01:23:53 UTC

Build move to 5.1

Comment 6 Randy MacLeod 2025-05-01 14:07:07 UTC

Bulk move of all unassigned 5.2 medium importance bugs to 5.3.

Comment 7 Maxin B. John 2025-06-09 12:57:58 UTC

Fix for the RISC-V "textrel" issue is present in binutils-2.41 release(from nanbield):

225df051d3d [PR ld/22263][PR ld/25694] RISC-V: Avoid dynamic TLS relocs in PIE.

( Bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=25694 )

Comment 8 Maxin B. John 2025-06-09 13:31:16 UTC

IMHO, this bug can be closed as RESOLVED->OBSOLETE.