I have an old Rails 2.3.2 application that I just ported to my new Mac running OS X Lion.
When I launch the server (script/server) it prints out the following two lines
[2012-01-05 18:19:26] INFO WEBrick 1.3.1
[2012-01-05 18:19:26] INFO ruby 1.8.7 (2011-02-18) [i686-darwin9.8.0]
but then there is a very long delay before it prints out:
[2012-01-05 18:20:26] INFO WEBrick::HTTPServer#start: pid=5792 port=3000
There must be something wrong.
How can I fix this problem?
It turns out that the compiler for Lion for Ruby has changed and Developer Tools 4.2 does not include it so I had to download the fix.
From here:
If you're running a fresh copy of Lion & Xcode 4.2, you're going to need to install the GCC 4.2 dev libraries first - they aren't included in a fresh Xcode 4.2 install.
Once I recompiled my Ruby then everything worked properly.
Related
It showing this error while install mongodb0community#5.0 / 6.0
When you update Ventura It will update Command line tool to 14.1.0.
In Xcode 14.1.0 is RC version so this version will not show in app store you have to download from the https://developer.apple.com/download/all/
Make sure your xcode and command line tool have same version otherwise it will show above error.
I upgraded both to 14.1.0
It work's perfectly 👍
The plugin had been working beautifully up until last night. Getting the following errors on iOS only after updating to latest Ionic/Cordova (android is fine).
Updated to:
xcode version 7.2.1
ionic version 1.7.14
I have also tested the same app with another mac running previous version of ionic 1.7.13 and cordova 6, and all is good.
After testing with the older version, i built a new mac (fresh wives laptop) with the latest ionic setup and again same error.
Here's the plugin in question https://ionicthemes.com/tutorials/about/native-facebook-login-with-ionic-framework
The following build commands failed:
CompileC build/testFresh.build/Debug-iphonesimulator/testFresh.build/Objects-normal/i386/FacebookConnectPlugin.o testFresh/Plugins/phonegap-facebook-plugin/FacebookConnectPlugin.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
ERROR running one or more of the platforms: Error code 65 for command: xcodebuild with args: -xcconfig,/Applications/AMPPS/www/ionic/testFresh/platforms/ios/cordova/build-debug.xcconfig,-project,testFresh.xcodeproj,ARCHS=i386,-target,testFresh,-configuration,Debug,-sdk,iphonesimulator,build,VALID_ARCHS=i386,CONFIGURATION_BUILD_DIR=/Applications/AMPPS/www/ionic/testFresh/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Applications/AMPPS/www/ionic/testFresh/platforms/ios/build/sharedpch
You may not have the required environment or OS to run this project
After banging my head against a wall for a few days, I found that others were having the same issue though it was labeled as a "cordova 6" problem.
Original github issue:
https://github.com/Wizcorp/phonegap-facebook-plugin/issues/1227
Eventually whilst scrolling through known bugs under github for "phonegap-facebook-plugin" i noticed that similar errors had occurred on a previous release, then super Jeduan re-wrote the plugin and released it under the following:
Plugin fix:
https://github.com/jeduan/cordova-plugin-facebook4
The above appears to be working find under cordova 6, xcode version 7.2.1 and ionic version 1.7.14
I have this error when I build the project on Iphone :
Warning: usage of --preserve-metadata with option "resource-rules" (deprecated in Mac OS X >= 10.10)!
/Users/Tom/Library/Developer/Xcode/DerivedData/Test-bwacbfyhutgdvnhetuiouvtcvvfi/Build/Products/Debug-iphoneos/Test.app/Frameworks/SKMaps.framework: invalid resource specification rule(s)
Command /usr/bin/codesign failed with exit code 1
If I built the project with the iOS Simulator, it run perfectly
I Work with swift 1.2 - Xcode 6.3.1 and OSX 10.10.3
Thank you for your help !
Ysee
EDIT :
I solved this problem, I had to manually install Skobbler SDK then I tested the installation with cocoapods. This works perfectly!
I solved this problem, I had to manually install Skobbler SDK then I tested the installation with cocoapods. This works perfectly!
If you work with Swift don't forget to add #import "SKMaps/SKMaps.h" in your Bridging-Header.h
Ysee
I'm trying to configure my development environment in my Mac with Xamarin and MonoGame but when I tried to add "MonoGame_3.0.1.mpack" in the Add-in Manager I got this error:
The Packacge 'Core v4.0' could not be found in any repository
The Packacge 'Ide v4.0' could not be found in any repository
This what I have installed on my Mac with no errors:
-Installed XamarinStudio
-Installed MonoFramework-MDK-3.8.0.macos10.xamarin.x86.pkg
-Installed MonoFramework-MRE-3.8.0.macos10.xamarin.x86.pkg
I'll really appreciate if any of you knows how can install MonoGame_3.0.1.mpack in Xamarin on Mac OS x
The issue is that that version of the template is not compatible with the version of Xamarian Studio you have installed. Until the newest version of Xamarian Studio is released for Mac, you won't be able to install that template.
However, you can download the template from here. It is compatible with the Mac OS X build version 5.5.2 of Xamarian Studio.
I am trying everything I can for the last 3 days and I didnt find a way to make this version of their SDK work with the latest unity version (4.3.1).
FB SDK version 4.2.4 works fine on every Unity version I tried, but, 4.3.6 doesnt work with any of them (4.0, 4.1, 4.2 and 4.3).
Always gives me that weird message about java building:
Error building Player: Win32Exception: ApplicationName='C:Program
Files (x86)Javajre7binjavac.exe', CommandLine='-bootclasspath
"E:/adt-bundle-windows/sdk/platforms/android-14android.jar" -d
"E:Unity Projects[project name]TempStagingAreabinclasses" -source 1.6
-target 1.6 -encoding ascii "comfacebookandroidR.java" "comwinterbigbangR.java"', CurrentDirectory='E:Unity Projects[project
name]TempStagingAreagen
Another weird thing, I setup my app to android 2.3.3 (API-10) why the hell it is trying to use android14?
With the combination of Unity 4.3.1 and FB SDK 4.2.4, I finally made it work flawless, but, I think that Ill be missing some good stuff from 4.3.6...
After almost a week long I think I found the problem.
I uninstalled all Java from my computer and installed Java 6 32bits. Now everything works as intended.