Changes between Initial Version and Version 1 of Ticket #54773, comment 10
- Timestamp:
- Sep 10, 2017, 6:34:27 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #54773, comment 10
initial v1 3 3 Nope. There's no reason for it to be done at that level. I'm saying you could change gcc (just like you are proposing with your patch) to include the full path. Eg: 4 4 5 {{{ 5 6 #define ASM_OPTIONS "-q --clang=/opt/local/bin/clang-mp-5.0" 7 }}} 6 8 7 9 Then anyone using gcc would spawn 'as -q --clang=/opt/local/bin/clang-mp-5.0" … … 9 11 Alternatively, create a separate port that provides /opt/local/bin/clang-as and have that port depend on both cctools and a specific version of clang such that it just does: 10 12 11 #!/bin/sh 12 exec @@PREFIX@@/bin/as -q --clang=@@PREFIX@@/bin/clang-mp-@@CLANG_VERSION@@ "${@}" 13 13 {{{ 14 #!/bin/sh 15 exec @@PREFIX@@/bin/as -q --clang=@@PREFIX@@/bin/clang-mp-@@CLANG_VERSION@@ "${@}" 16 }}} 14 17 Or we can breakup the cctools port into separate ports such that install_name_tool and as are provided by separate ports, allowing the llvm ports to depend on install_name_tool and the as port to depend on clang.