Opened 10 years ago
Closed 10 years ago
#41099 closed defect (fixed)
libANN: error: C++ requires a type specifier for all declarations
| Reported by: | basmac | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.0 |
| Keywords: | mavericks | Cc: | jwhowse4, zifu.wong@…, hielsber@…, ryandesign (Ryan Carsten Schmidt) |
| Port: | libANN |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Clean Mavericks install with Xcode and CLI latest versions.
Made fine in 10.8.5
debug file attached
Attachments (1)
Change History (9)
Changed 10 years ago by basmac
| Attachment: | libANN.log added |
|---|
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | mnick@… removed |
|---|---|
| Description: | modified (diff) |
| Keywords: | mavericks added; libANN removed |
| Owner: | changed from macports-tickets@… to mnick@… |
| Summary: | libANN fails to build Mavericks → libANN: error: C++ requires a type specifier for all declarations |
comment:3 follow-up: 4 Changed 10 years ago by stigfinnaren@…
What sort of timeframe is implied by normal priority?
comment:4 follow-up: 5 Changed 10 years ago by danielluke (Daniel J. Luke)
Replying to stigfinnaren@…:
What sort of timeframe is implied by normal priority?
no timeframe is implied by any priority. If you want something fixed you can either help figure out how to fix it, wait patiently while someone else fixes it for you for free, or find someone who you can pay to fix it for you.
comment:5 follow-up: 8 Changed 10 years ago by hielsber@…
Replying to dluke@…:
Replying to stigfinnaren@…:
What sort of timeframe is implied by normal priority?
no timeframe is implied by any priority. If you want something fixed you can either help figure out how to fix it, wait patiently while someone else fixes it for you for free, or find someone who you can pay to fix it for you.
I fixed this issue on my system by simply adding the return type int to the main definition at the bottom of /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_libANN/libANN/work/ann_1.1.2/ann2fig/ann2fig.cpp. The path may or may not be different on your system, but it is given in the log file in any case.
comment:6 Changed 10 years ago by mf2k (Frank Schima)
| Owner: | changed from mnick@… to macports-tickets@… |
|---|
mnick has retired.
comment:7 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | jwhowse4@… added |
|---|
Has duplicate #42015.
comment:8 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | zifu.wong@… hielsber@… ryandesign@… added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Replying to hielsber@…:
I fixed this issue on my system by simply adding the return type int to the main definition at the bottom of /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_libANN/libANN/work/ann_1.1.2/ann2fig/ann2fig.cpp. The path may or may not be different on your system, but it is given in the log file in any case.
Thanks. Fixed in r115518.
I see that the error here is:
Probably the reason we did not see this on previous versions of OS X is that because the port is not UsingTheRightCompiler (nor
-archflags, for that matter) it was not using clang until now.