Discussion:
installation issue on osx10.8
(too old to reply)
w***@gmail.com
2017-06-21 17:20:14 UTC
Permalink
james, could you look at this, sir? at a guess, their curl is old??


https://forum.flightgear.org/viewtopic.php?f=21&t=32397

[quote]
I have been trying to install Flightgear on my imac running 10.8.5 - so far I
have tried Flightdear versions 2017.1.2 and 2017.2.1, but both fail in the same
place with the same error. The initial gui loads for about half a second then
crashes, the log saying this:

Process: fgfs [21740]
Path: /Applications/FlightGear.app/Contents/MacOS/fgfs
Identifier: org.flightgear.FlightGear
Version: 2017.2.1 (2017.2.1)
Code Type: X86-64 (Native)
Parent Process: launchd [407]
User ID: 501

Date/Time: 2017-06-20 06:48:00.001 +0100
OS Version: Mac OS X 10.8.5 (12F2560)
Report Version: 10

Interval Since Last Report: 12071090 sec
Crashes Since Last Report: 4060
Per-App Interval Since Last Report: 126 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 01AA6C7C-268F-C8B7-368B-3607F126A031

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Dyld Error Message:
Symbol not found: _curl_multi_wait
Referenced from: /Applications/FlightGear.app/Contents/MacOS/fgfs
Expected in: /usr/lib/libcurl.4.dylib

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 dyld 0x00007fff676b109d dyld_fatal_error + 1
1 dyld 0x00007fff676b4048 dyld::fastBindLazySymbol(ImageLoader**, unsigned long)
+ 139
2 libdyld.dylib 0x00007fff8ff478ee dyld_stub_binder_ + 13
3 ??? 0x0000000108ac4030 0 + 4440473648
4 org.flightgear.FlightGear 0x000000010834c82c
SGSubsystemGroup::Member::update(double) + 76
5 org.flightgear.FlightGear 0x000000010834bace SGSubsystemGroup::update(double)
+ 302
6 org.flightgear.FlightGear 0x000000010834d57e SGSubsystemMgr::update(double) + 46
7 org.qt-project.QtCore 0x000000010b43b3e2 QMetaObject::activate(QObject*, int,
int, void**) + 1986
8 org.qt-project.QtCore 0x000000010b4340f0 QObject::event(QEvent*) + 48
9 org.qt-project.QtWidgets 0x000000010a102ddb
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
10 org.qt-project.QtWidgets 0x000000010a1060f8 QApplication::notify(QObject*,
QEvent*) + 8136
11 org.qt-project.QtCore 0x000000010b408da3
QCoreApplication::notifyInternal(QObject*, QEvent*) + 115
12 org.qt-project.QtCore 0x000000010b45d196 QTimerInfoList::activateTimers() + 1270
13 libqcocoa.dylib 0x000000010cca57a2 0x10cc86000 + 128930
14 com.apple.CoreFoundation 0x00007fff8bd3cb31
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
15 com.apple.CoreFoundation 0x00007fff8bd3c455 __CFRunLoopDoSources0 + 245
16 com.apple.CoreFoundation 0x00007fff8bd5f7f5 __CFRunLoopRun + 789
17 com.apple.CoreFoundation 0x00007fff8bd5f0e2 CFRunLoopRunSpecific + 290
18 com.apple.HIToolbox 0x00007fff88ddceb4 RunCurrentEventLoopInMode + 209
19 com.apple.HIToolbox 0x00007fff88ddcc52 ReceiveNextEventCommon + 356
20 com.apple.HIToolbox 0x00007fff88ddcae3 BlockUntilNextEventMatchingListInMode + 62
21 com.apple.AppKit 0x00007fff89a27533 _DPSNextEvent + 685
22 com.apple.AppKit 0x00007fff89a26df2 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
23 com.apple.AppKit 0x00007fff89a1e1a3 -[NSApplication run] + 517
24 libqcocoa.dylib 0x000000010cca63bd 0x10cc86000 + 132029
25 org.qt-project.QtCore 0x000000010b40639d
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 381
26 org.qt-project.QtCore 0x000000010b40937a QCoreApplication::exec() + 346
27 org.flightgear.FlightGear 0x000000010864a2d6 flightgear::runLauncherDialog()
+ 1462
28 org.flightgear.FlightGear 0x0000000107af065d fgMainInit(int, char**) + 3117
29 org.flightgear.FlightGear 0x0000000107ab9a1d main + 253
30 org.flightgear.FlightGear 0x0000000107ab9734 start + 52

Any ideas what I can do to get it working? I've searched all over for any info
but found nothing.
thanks!
[/quote]
--
NOTE: No off-list assistance is given without prior approval.
*Please keep mailing list traffic on the list unless*
*a signed and pre-paid contract is in effect with us.*
James Turner
2017-06-21 21:39:53 UTC
Permalink
Post by w***@gmail.com
james, could you look at this, sir? at a guess, their curl is old??
https://forum.flightgear.org/viewtopic.php?f=21&t=32397 <https://forum.flightgear.org/viewtopic.php?f=21&t=32397>
[quote]
Hmm, there’s no good answer there, either we drop 10.8 (and earlier) support, or we have to conditionally use this curl feature, and that’s kind of awkward, bordering on ‘impossible’; I can’t face shipping our own version of Curl just to support ancient versions of OS-X.

Kind regards,
James
James Turner
2017-06-21 21:51:54 UTC
Permalink
Post by James Turner
Hmm, there’s no good answer there, either we drop 10.8 (and earlier) support, or we have to conditionally use this curl feature, and that’s kind of awkward, bordering on ‘impossible’; I can’t face shipping our own version of Curl just to support ancient versions of OS-X.
Ah it looks a bit less impossible than I thought, from some quick reading - we just have to do something either more awkward (call select(3) manually with some issues) or less efficient (wait for a fixed amount of time and poll curl instead of waiting on the FDs)

I’ll think over which solution is less hacky - easiest would be to use the solution on all version of Mac, to avoid having to dlopen that symbol, on certain versions. But if we’re using it everywhere, it can’t be /too/ ugly - the HTTP thread runs forever.

Kind regards,
James
w***@gmail.com
2017-06-22 01:07:45 UTC
Permalink
I’ll think over which solution is less hacky - easiest would be to use the
solution on all version of Mac, to avoid having to dlopen that symbol, on
certain versions. But if we’re using it everywhere, it can’t be /too/ ugly -
the HTTP thread runs forever.
whatever you decide... i don't know mac stuffs but i expect that some versions
just pass their EOL date... kinda like trying to support ubuntu 14.04 LTS until
2019 ;)
--
NOTE: No off-list assistance is given without prior approval.
*Please keep mailing list traffic on the list unless*
*a signed and pre-paid contract is in effect with us.*
James Turner
2017-06-28 09:22:05 UTC
Permalink
I’ll think over which solution is less hacky - easiest would be to use the solution on all version of Mac, to avoid having to dlopen that symbol, on certain versions. But if we’re using it everywhere, it can’t be /too/ ugly - the HTTP thread runs forever.
I pushed a fix for this in SimGear commit:

47842c9ea7d546c554acee86d7dc0bad323a8d81

It could also be ported to the release branch if we plan to make another 2017.2 release - do we?

In the meantime it would be good if the affected users can verify this gets us working on macOS 10.8 for them.

Kind regards,
James

Loading...