Opened 8 years ago
Last modified 8 years ago
#50254 closed defect
harfbuzz-icu @1.1.2: error: unrecognized command line option "-std=c++0x" — at Version 2
| Reported by: | fortran_cc@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.4 |
| Keywords: | lion | Cc: | |
| Port: | harfbuzz-icu |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
---> Computing dependencies for harfbuzz-icu
---> Building harfbuzz-icu
Error: org.macports.build for port harfbuzz-icu returned: command execution failed
Please see the log file for port harfbuzz-icu for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_harfbuzz/harfbuzz-icu/main.log
Error: Problem while installing harfbuzz-icu
Change History (3)
Changed 8 years ago by fortran_cc@…
comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Owner: | changed from macports-tickets@… to ryandesign@… |
| Port: | harfbuzz-icu added |
| Summary: | Error: org.macports.build for port harfbuzz-icu returned: command execution failed → harfbuzz-icu @1.1.2: error: unrecognized command line option "-std=c++0x" |
I see that you're on Lion, that MacPorts has chosen to use the llvm-g++ compiler, and that it does not understand the "-std=c++0x" flag. I am not surprised llvm-g++ doesn't understand that flag, but I am surprised MacPorts chose to use llvm-g++. What version of Xcode is installed (find out by getting info on Xcode.app), and what version of clang? (find out by running "clang -v")
comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|
Note: See
TracTickets for help on using
tickets.
main.log