bsd.port.mk: do not define STRIP in the configure or build environments
AcceptedPublic
Actions

Authored by royger on Jun 23 2026, 7:59 AM.

Tags

None

Referenced Files

	F163574519: D57764.diff
	Fri, Jul 24, 3:34 PM

	F163574451: D57764.diff
	Fri, Jul 24, 3:34 PM

	Unknown Object (File)
	Mon, Jul 20, 7:37 AM

	Unknown Object (File)
	Sun, Jul 19, 3:24 PM

	Unknown Object (File)
	Sun, Jul 19, 3:24 PM

	Unknown Object (File)
	Sun, Jul 19, 3:23 PM

	Unknown Object (File)
	Sun, Jul 19, 3:23 PM

	Unknown Object (File)
	Sun, Jul 19, 2:05 PM

View All 19 Files

Subscribers

None

Details

Reviewers

fuz

Group Reviewers

portmgr

Summary

STRIP has a different meaning when using bsd.lib.mk, and hence defining it as the path to the strip binary in the environment causes existing ports to break. Revert part of cb0504025c42 and define the path to the strip binary using STRIP_CMD instead of plain STRIP.

Fixes: cb0504025c42 ("bsd.port.mk: also export GNU strip when USE_BINUTILS is set")

Diff Detail

Repository

R11 FreeBSD ports repository

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

royger requested review of this revision.Jun 23 2026, 7:59 AM

royger created this revision.

royger mentioned this in D55509: bsd.port.mk: also export GNU strip when USE_BINUTILS is set.

Looks good to me. I think portmgr needs to be looped in, too.

This revision is now accepted and ready to land.Jun 23 2026, 8:46 AM

Done, was waiting to add them to confirm you think this is the right fix.

Revision Contents
Changeset List

Path

Size

Mk/

bsd.port.mk

4 lines

Diff 180354

View Options

bsd.port.mk: do not define STRIP in the configure or build environmentsAcceptedPublicActions