#53996 closed defect (fixed)
ostinato @0.8 fails to build with libc++
| Reported by: | 1-61803 | Owned by: | g5pw (Aljaž Srebrnič) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | ostinato |
Description
Attachments (2)
Change History (12)
Changed 8 years ago by 1-61803
| Attachment: | ostinato_failed_main.log added |
|---|
comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | set to g5pw |
|---|---|
| Status: | new → assigned |
Changed 8 years ago by 1-61803
| Attachment: | ostinato_failed_2_main.log added |
|---|
comment:3 Changed 8 years ago by kencu (Ken)
In the log above, the build is still using /usr/bin/clang, and it's not building with clang-3.9 w libc++. qt4 caches it's build info into some convoluted configuration files (and more than one, to make it trickier). I can recall needing to change these by hand when I changed compilers from clang-3.7 to clang-3.8, but maybe there's an easier way.
comment:4 Changed 8 years ago by 1-61803
Thanks for spotting that. I'll try to reinstall qt4-mac and report back.
comment:5 Changed 8 years ago by kencu (Ken)
Just built it on 10.6, and seems to build and run OK, although I have no way to know if it actually all works properly.
$ port -v installed ostinato The following ports are currently installed: ostinato @0.8_0 (active) platform='darwin 10' archs='x86_64' date='2017-04-21T11:13:17-0700'
comment:6 Changed 8 years ago by 1-61803
It built on 10.8 too with clang-3.9 and libc++ (see ticket:53994#comment:3). The application launches, I haven't fully tested it though. Thanks again Ken.
comment:7 Changed 8 years ago by kencu (Ken)
So - a workaround, again, but what we really need is a proper portfile fix. I defer to g5pw, but it would appear that ostinato needs some newer clang version than the clang-3.4-ish version that comes with 10.8. But to make it build with this newer clang version, it looks like that needs to get baked into qt4 during the build of qt4-mac. This is a bit messy. Does the qmake portgroup take care of something like this?
comment:8 follow-up: 9 Changed 5 years ago by kencu (Ken)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
fixed with refinements to everything (base, compiler selection, defaulting to libc++, qt4-mac).
comment:9 Changed 5 years ago by 1-61803
Replying to kencu:
fixed with refinements to everything (base, compiler selection, defaulting to libc++, qt4-mac).
thx, I couldn't see a commit though, can you provide a link for the fix?
comment:10 Changed 5 years ago by kencu (Ken)
no single commit to reference. please reopen if you find it's still an issue (or better new ticket /new log as so much has changed).
This port uses the qt4 portgroup. I'd expect that portgroup to properly handle the necessary details of supplying the C++ library flags. Or, maybe it needs to be using the qmake portgroup instead, which looks like it does handle that.