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)
Mon, Jan 20, 4:23 PM
Unknown Object (File)
Thu, Jan 16, 7:31 AM
Unknown Object (File)
Jan 6 2025, 4:37 PM
Unknown Object (File)
Jan 5 2025, 11:07 AM
Unknown Object (File)
Jan 3 2025, 10:19 AM
Unknown Object (File)
Nov 25 2024, 10:20 AM
Unknown Object (File)
Nov 22 2024, 3:15 PM
Unknown Object (File)
Nov 20 2024, 2:15 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 21516
Build 20829: 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.