Opened 4 years ago
Closed 4 years ago
#62799 closed defect (fixed)
llvm-11: legacy-support is specified as a build-only dependency but behaving as a run or lib dependency
Reported by: | kencu (Ken) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | llvm-11 legacy-support |
Description
when legacy-support is used as a build dependency and links statically, as it does in llvm/clang-11, then those ports should not be tied to legacy-support after the build, and they should not complain if it is being deactivated, as they no longer need it.
However, they do complain:
$ sudo port deactivate legacy-support Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. The following ports will break: llvm-11 @11.1.0_0 clang-11 @11.1.0_1
Change History (5)
comment:1 follow-up: 3 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 4 years ago by kencu (Ken)
Port: | llvm-11 added |
---|---|
Summary: | legacy-support: build-only dependency not working? → llvm-11: legacy-support is specified as a build-only dependency but behaving as a run or lib dependency |
comment:3 Changed 4 years ago by jmroot (Joshua Root)
Replying to ryandesign:
Then I guess legacy-support is being added as a lib or run dependency, instead of as a build dependency as you intended.
Or was when the port was installed, at least.
comment:4 Changed 4 years ago by kencu (Ken)
rebuilding it now to see if something has changed since it was installed.
comment:5 Changed 4 years ago by kencu (Ken)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Yes, rebuilding clang-11 and just simply reinstalling llvm-11 fixed this.
Note: See
TracTickets for help on using
tickets.
Then I guess legacy-support is being added as a lib or run dependency, instead of as a build dependency as you intended.