Opened 10 years ago
Last modified 7 years ago
#43815 closed defect
clisp @2.49: error: unknown argument: '-R/opt/local/lib' — at Version 1
| Reported by: | wanghuan1406@… | Owned by: | easieste@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.0 |
| Keywords: | Cc: | ryandesign@… | |
| Port: | clisp |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
hello there
i failed to install common lisp on osx 10.9.3, the returned error is about clang
:info:build clang: error: unknown argument: '-R/opt/local/lib' [-Wunused-command-line-argument-hard-error-in-future]
i've tried set root $ARCHFLAGS, by
export ARCHFLAGS="-Wno-error=unused-command-line-argument-hard-error-in-future"
but nothing works.
please help me, thx in advanced
Change History (3)
Changed 10 years ago by wanghuan1406@…
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Description: | modified (diff) |
| Keywords: | clisp clang 10.9.3 mavericks removed |
| Milestone: | MacPorts Future |
| Owner: | changed from macports-tickets@… to easieste@… |
| Summary: | failed to install clisp 2.49 on OSX 10.9.3 → clisp @2.49: error: unknown argument: '-R/opt/local/lib' |
MacPorts deliberately ignores environment variables you set on the command line, so that won't help.
We need to remove the -R flag from wherever it's being inserted. It has never been supported, using it has been printing a warning for some time, and now with the latest clang it is an error to attempt to use it.
The portfile says clang is blacklisted, but doesn't say why exactly:
# Likely a project bug # TODO: Report upstream and provide a link to the bug report here. compiler.blacklist *clang*
Note from the attached log that the port is erroneously using /usr/bin/cc; as of Xcode 5, that'll be clang. The port should be UsingTheRightCompiler, and also whatever clang incompatibilities exist in clisp need to be fixed.
wanghuan1406, I cannot see from the log where this compiler choice is being set, because this was not a clean build. Please clean and try again and attach the new main.log file.
main.log