Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#41460 closed defect (fixed)

xtide @2.11: error: no viable overloaded '='

Reported by: macports-trac@… Owned by: jberry@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: mavericks Cc: ryandesign (Ryan Carsten Schmidt)
Port: xtide

Description

xtide configures but fails to build on Mavericks. Log file attached

Attachments (4)

main.log (379.3 KB) - added by macports-trac@… 10 years ago.
Log file showing xtide build failure on Mac OS 10.9
xtide-2.13.2.diff (3.0 KB) - added by ryandesign (Ryan Carsten Schmidt) 10 years ago.
in-progress patch
xtide-2.13.2-builds.diff (3.3 KB) - added by ryandesign (Ryan Carsten Schmidt) 10 years ago.
revised patch that builds (but doesn't destroot)
patch-configure.ac.diff (1.4 KB) - added by ryandesign (Ryan Carsten Schmidt) 10 years ago.

Download all attachments as: .zip

Change History (12)

Changed 10 years ago by macports-trac@…

Attachment: main.log added

Log file showing xtide build failure on Mac OS 10.9

comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Keywords: mavericks added
Owner: changed from macports-tickets@… to jberry@…
Port: xtide added
Summary: xtide does not install on Mac OS 10.9xtide @2.11: error: no viable overloaded '='

James, xtide 2.13.2 is available upstream; maybe updating the port will fix this issue. You should also fix the livecheck.

comment:2 in reply to:  1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign@…:

You should also fix the livecheck.

r114007

comment:3 in reply to:  1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign@…:

xtide 2.13.2 is available upstream;

It fails to configure, erroneously thinking that clang is older than GCC 4.4 (which is apparently the minimum requirement). I've emailed the developer about this error.

Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: xtide-2.13.2.diff added

in-progress patch

Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: xtide-2.13.2-builds.diff added

revised patch that builds (but doesn't destroot)

Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: patch-configure.ac.diff added

comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

The developer sent me a revised configure script which works with clang; the build succeeds too. New patches attached.

The destroot fails because the updated harmonics distribution has changed its layout. I could fix this easily, but it might be better for the harmonics to be their own subport so that they can be updated independently of the program, declare their own license and homepage, etc. James, do you have any objection to that? If not, what should the subport be called? Is just "xtide-harmonics" reasonable? Or is "xtide-data" ok? (We already have several other "-data" ports so this might be preferable.) I'll make the xtide port depend on this new subport. Since the filenames are changing with the new version of the harmonics data, it's easier to separate this out into a subport now, rather than wait til later when we'd need to use the deactivate hack.

comment:5 Changed 10 years ago by jberry@…

Hi Ryan. Thanks for the thoughts. I've got to admit I haven't used this port in quite a while and haven't really kept up with the discussion.... so I think you should do as you see fit. And while you're at it, feel free to remove me as maintainer of the port, as I'm clearly being more of a hindrance than a help at the moment.

comment:6 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

Ok, here we go! r114196

comment:7 Changed 10 years ago by jmroot (Joshua Root)

You do realise that the C++11 requirement means this is now broken on everything other than Mavericks?

comment:8 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Nope, I did not realize it now requires C++11. We could make the port build with gcc48 on pre-Mavericks, and/or we could report the problem to the developers.

Note: See TracTickets for help on using tickets.