Page MenuHomeFreeBSD

Restore ${OBJDUMP}
AbandonedPublic

Authored by brooks on Mar 8 2024, 12:15 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 20, 6:40 AM
Unknown Object (File)
Fri, Dec 6, 12:41 AM
Unknown Object (File)
Tue, Dec 3, 11:40 PM
Unknown Object (File)
Oct 2 2024, 2:13 PM
Unknown Object (File)
Sep 25 2024, 1:54 PM
Unknown Object (File)
Sep 17 2024, 7:48 PM
Unknown Object (File)
Sep 4 2024, 6:41 AM
Unknown Object (File)
Aug 23 2024, 12:24 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