Re: MacOSX 10.6 relocatable application bundle: tries to load /usr/lib/libc++.1.dylib on Snow Leopard

Jochem Liem <[email protected]>
Newsgroups gmane.comp.ai.prolog.swi
Message-ID <CABryw9RuR7HDQuzH0qDPDEP8KR6TBA-m72wX=KeowXcen0SJUQ@mail.gmail.com>
Hi Jan,

The commandline versions function perfectly. I agree that it is
wasteful to spend time supporting 10.6.
I think indicating on the download page that the application bundle
requires 10.7 (or later) should suffice.

Cheers,
Jochem




On Thu, Nov 21, 2013 at 1:17 PM, Jan Wielemaker <[email protected]> wrote:
> On 11/21/2013 09:05 AM, Jochem Liem wrote:
>>
>> Dear all,
>>
>> On my MacOSX Snow Leopard (10.6.8) machine the SWI-Prolog relocatable
>> application bundle crashes on startup. It tries to load
>> /usr/lib/libc++.1.dylib according to the crash report (see below).
>>
>> On MacOSX Mavericks (10.9) I can start the application bundle without
>> any problems.
>>
>> I'm planning of upgrading the Snow Leopard machine tomorrow, but I
>> thought it was worthwhile to test the application bundle.
>
>
> Thanks for the report Jochem.  It seems to be possible to create a 10.6
> version, but complicated.  See
>
> http://stackoverflow.com/questions/18160966/qt-5-cannot-deploy-on-snowleopard
>
> I'd assume that the commandline versions in the app (swipl) runs fine,
> right?
>
> I'm tempted to make a remark in the readme and leave it that way.  10.6
> should be close to dead and an upgrade to Maverics is free.  There are
> more useful things to do then supporting antique.
>
>         Cheers --- Jan
>
>
>>
>> Cheers,
>> Jochem
>>
>>
>> Process:         swipl-win [389]
>> Path:            /Applications/SWI-Prolog.app/Contents/MacOS/swipl-win
>> Identifier:      org.swi-prolog.swipl-win
>> Version:         ??? (???)
>> Code Type:       X86-64 (Native)
>> Parent Process:  launchd [94]
>>
>> Date/Time:       2013-11-21 09:51:30.214 +0200
>> OS Version:      Mac OS X 10.6.8 (10K549)
>> Report Version:  6
>>
>> Interval Since Last Report:          413419 sec
>> Crashes Since Last Report:           1
>> Per-App Crashes Since Last Report:   1
>> Anonymous UUID:                      D8DCF814-7276-499E-BED3-C20867560804
>>
>> Exception Type:  EXC_BREAKPOINT (SIGTRAP)
>> Exception Codes: 0x0000000000000002, 0x0000000000000000
>> Crashed Thread:  0
>>
>> Dyld Error Message:
>>    Library not loaded: /usr/lib/libc++.1.dylib
>>    Referenced from: /Applications/SWI-Prolog.app/Contents/MacOS/swipl-win
>>    Reason: image not found
>>
>> Binary Images:
>>      0x7fff5fc00000 -     0x7fff5fc3be0f  dyld 132.1 (???)
>> <29DECB19-0193-2575-D838-CF743F0400B2> /usr/lib/dyld
>>
>> Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core
>> 2 Duo, 2.53 GHz, 2 GB, SMC 1.47f2
>> Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
>> Memory Module: global_name
>> AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D),
>> Broadcom BCM43xx 1.0 (5.10.131.42.4)
>> Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
>> Network Service: AirPort, AirPort, en1
>> Serial ATA Device: OCZ-VERTEX2, 223.57 GB
>> Serial ATA Device: MATSHITADVD-R   UJ-868
>> USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24400000 / 2
>> USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.),
>> 0x0237, 0x04600000 / 3
>> USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x04500000 / 2
>> USB Device: Internal Memory Card Reader, 0x05ac  (Apple Inc.), 0x8403,
>> 0x26500000 / 2
>> USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000 / 2
>> USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.),
>> 0x8213, 0x06110000 / 3
>>
>



-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Jochem Liem, MSc.
Informatics Institute
Faculty of Science
University of Amsterdam
http://www.science.uva.nl/~jliem/

Mobile: +31 (0)6  4321 9992

Visitor address:
Science Park 904, C2.248
1098 XH Amsterdam

Mailing address:
Postbus 94323
1090 GH Amsterdam
The Netherlands
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.