Page MenuHomeFreeBSD

Hoist LDFLAGS_${ARCH} into bsd.port.mk
ClosedPublic

Authored by emaste on Sep 18 2018, 2:41 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 20, 1:22 PM
Unknown Object (File)
Fri, Apr 19, 7:24 PM
Unknown Object (File)
Dec 22 2023, 10:11 PM
Unknown Object (File)
Dec 13 2023, 8:30 AM
Unknown Object (File)
Nov 24 2023, 2:55 AM
Unknown Object (File)
Sep 2 2023, 9:10 AM
Unknown Object (File)
Jun 19 2023, 8:33 PM
Unknown Object (File)
Mar 12 2023, 10:32 PM
Subscribers

Details

Reviewers
bapt
Group Reviewers
portmgr

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

This revision is now accepted and ready to land.Sep 18 2018, 2:42 PM

while we are here I'd like to mention this relevant review which maybe some people have opinions on as well 😅

while we are here I'd like to mention this relevant review which maybe some people have opinions on as well 😅

Indeed, that approach would be convenient but some folks didn't like it :)

That said, I now think it doesn't matter much: LDFLAGS_i386=-Wl,-znotext perhaps has less semantic meaning, but is just as much of a nop as D16817 when ld.bfd is in use.

mat added inline comments.
Mk/bsd.port.mk
2065

technically, the .if is useless, and if it was supposed to be meaningful, it should probably be .if !empty(LDFLAGS_${ARCH})

emaste added inline comments.
Mk/bsd.port.mk
2065

I was just following the approach for ${lang}FLAGS_${ARCH} above. Shall I take the .if out?

emaste added inline comments.
Mk/bsd.port.mk
2065

(Please explicit Approved by: portmgr if so)

Mk/bsd.port.mk
2065

Yes, please, and the .if on line 2060, approved by portmgr.