Opened 10 years ago
Closed 10 years ago
#45899 closed defect (fixed)
terminal-notifier: fails to build
Reported by: | petrrr | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.2 |
Keywords: | Cc: | ||
Port: | terminal-notifier |
Description
I cannot update from 1.6.0 to 1.6.2, build fails on OSX 10.8.5. I attach a clean main.log.
% xcodebuild -version Xcode 4.6.2 Build version 4H1003 % port installed terminal-notifier The following ports are currently installed: terminal-notifier @1.6.0_0 (active) % port outdated terminal-notifier: The following installed ports are outdated: terminal-notifier 1.6.0_0 < 1.6.2_0
Attachments (1)
Change History (7)
Changed 10 years ago by petrrr
Attachment: | terminal-notifier.main.log added |
---|
comment:1 Changed 10 years ago by seanfarley (Sean Farley)
I'm the one that updated this but I have no idea from the log what is going on. Is something non-standard about your compilers / xcode?
comment:2 Changed 10 years ago by petrrr
As written above I am using Xcode 4.6.2. If I understand things right, Xcode 5 would also be an option on Mountain Lion (not sure where to get it), but not required as we support Xcode >= 4.4 on ML.
comment:3 Changed 10 years ago by raimue (Rainer Müller)
I don't have an installation of this version and can't deduce anything from the log. After the release of OS X 10.10 Yosemite, the older OS X 10.8 Mountain Lion is no longer a supported platform following our policy of supporting the latest release and the one before. Please understand that I won't investigate further. However, if you are able to provide a patch, I will be happy to commit it.
comment:4 Changed 10 years ago by petrrr
The port builds fine with Xcode 5.1.1, so at least with Xcode 4.6.2 this port breaks. Maybe the port should catch this.
petr% xcodebuild -version Xcode 5.1.1 Build version 5B1008 petr% port installed terminal-notifier The following ports are currently installed: terminal-notifier @1.6.2_0 (active)
comment:5 Changed 10 years ago by petrrr
Hi, I am wondering if we want to do something about this port. My understanding is that it was not building with 4.6.2 and the update to 5.1.1 solved this issue. So is this something we want to catch? Is there something like Xcode blacklisting?
Or do we just close as wontfix?
comment:6 Changed 10 years ago by raimue (Rainer Müller)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Based on the reports in this ticket, I added a minimum requirement on Xcode 5.0 for OS X 10.8 Mountain Lion in r131517.
main.log