-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for library not found for -lgcc_s.10.4
on MacOS Mojave Xcode 10
#33
Comments
I never compiled it with xcode, (I use command line tools from apple) Can you take a look if I made tests correctly |
To be clear, I never used Xcode either. Indeed I just used gem, as described above. (I do have all the Xcode tools installed and up to date as I do iOS development, but I didn’t open them as part of installing fast_excel). I try to keep a pretty vanilla environment, but perhaps this error I got was erroneous due to my setup or something (though libxlswriter does seem to discuss it in their issues). I just thought I’d report it in case someone else was hitting it. I know from other projects, I usually check the issues first if I hit something. Thanks for the response! |
Thanks @mikemee, that tip about linking libSystem.B.dylib to libgcc_s.10.4.dylib worked and doubtlessly saved me hours of frustration :) |
Any idea how to make it work well for Xcode? Maybe change something in compile scripts? |
@Paxa My research suggested that updating the Libxlsxwriter version used by fast_excel would fix the problems. |
When I did a
gem install fast_excel
on macOS Mojave and Xcode 10, I was getting the error:After a bit of digging, I found this fix which allowed the install to proceed as expected:
$ cd /usr/local/lib $ sudo ln -s ../../lib/libSystem.B.dylib libgcc_s.10.4.dylib
I think this might be fixed by updating to a more recent
Libxlsxwriter
. It seems to be related to macOS deprecating something, and the latestLibxlsxwriter
seems to account for this in their build scripts updated for Xcode 10.FYI in case someone else hits this and/or it can be corrected...
The text was updated successfully, but these errors were encountered: