Page MenuHomeFreeBSD

USES=cargo to respect CC for linking
ClosedPublic

Authored by jbeich on Dec 12 2018, 4:07 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 22, 2:50 AM
Unknown Object (File)
Sun, Nov 9, 1:25 AM
Unknown Object (File)
Fri, Nov 7, 5:46 AM
Unknown Object (File)
Tue, Nov 4, 1:06 AM
Unknown Object (File)
Tue, Nov 4, 12:58 AM
Unknown Object (File)
Sep 13 2025, 10:19 AM
Unknown Object (File)
Sep 12 2025, 11:06 PM
Unknown Object (File)
Sep 9 2025, 3:14 AM
Subscribers

Details

Reviewers
None
Group Reviewers
rust
O5: Ports Framework(Owns No Changed Paths)
portmgr
Commits
rP487455: USES=cargo to respect CC for linking
Summary

No consumers change CC atm but if users do something like CC=ccache gcc9 build will fail as -C linker appears to only accept command (found via PATH) or absolute path.

Test Plan

Diff Detail

Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 21515
Build 20828: arc lint + arc unit

Event Timeline

jbeich removed a reviewer: portmgr.

Oops, drop repository type. We don't need portmgr in this review. ;)

Hmm, I guess it's ok.

Do you have any example use cases in mind for overriding the linker driver?

I build base and ports using devel/llvm60 and /usr/bin/cc doesn't exist. The binary rust package seems to have /usr/bin/cc hardcoded and can't build any rust ports without this change. (Firefox does build, but that's because its build scripts add -C linker.)

This revision was not accepted when it landed; it landed in state Needs Review.Dec 14 2018, 6:20 PM
This revision was automatically updated to reflect the committed changes.