Page MenuHomeFreeBSD

Restore ${OBJDUMP}
AbandonedPublic

Authored by brooks on Mar 8 2024, 12:15 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Feb 27, 8:07 PM
Unknown Object (File)
Wed, Feb 26, 10:20 PM
Unknown Object (File)
Feb 2 2025, 5:18 PM
Unknown Object (File)
Jan 24 2025, 10:11 AM
Unknown Object (File)
Jan 16 2025, 12:35 PM
Unknown Object (File)
Jan 13 2025, 9:03 PM
Unknown Object (File)
Jan 2 2025, 9:09 PM
Unknown Object (File)
Dec 30 2024, 8:54 PM
Subscribers

Details

Summary

Define an OBJDUMP variable and prefer the cross tools version where
available. Allow XOBJDUMP to override and search for llvm-objdump in
CROSS_BINUTILS_PREFIX to maximize our chances of finding one.

A future commit will use objdump to compare the set of symbols built in
libraries with a reference list.

This reverts commit fd406aa3de47e89456febcaf6cb65d22a6317bc1

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 56512
Build 53400: arc lint + arc unit

Event Timeline

This revision is now accepted and ready to land.Mar 19 2024, 5:00 PM

A future commit will use objdump to compare the set of symbols built in libraries with a reference list.

No objection, but is there a reason we cannot use nm and/or readelf?

A future commit will use objdump to compare the set of symbols built in libraries with a reference list.

No objection, but is there a reason we cannot use nm and/or readelf?

I thought of objdump first. :) After a recent NetBSD post of someone doing something similar with nm I looked at it and nm flags are a portability nightmare (see my follow up email). readelf also has issues (llvm-readelf lacks --use-dynamic), but looking it over I think things might better than using objdump. I'll see about switching to readelf.

I'm going to switch to using readelf