git error “unable to locate xcodebuild” after a fresh OS X Mavericks upgrade
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
When I try to run previously working git commands, I get this:
dyld: Symbol not found: _sqlite3_intarray_bind
Referenced from: /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
Expected in: /opt/local/lib/libsqlite3.dylib
in /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
git: error: unable to locate xcodebuild, please make sure the path to the Xcode folder is set correctly!
git: error: You can set the path to the Xcode folder using /usr/bin/xcode-select -switch
How can I fix this?
git xcodebuild osx-mavericks
add a comment |
When I try to run previously working git commands, I get this:
dyld: Symbol not found: _sqlite3_intarray_bind
Referenced from: /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
Expected in: /opt/local/lib/libsqlite3.dylib
in /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
git: error: unable to locate xcodebuild, please make sure the path to the Xcode folder is set correctly!
git: error: You can set the path to the Xcode folder using /usr/bin/xcode-select -switch
How can I fix this?
git xcodebuild osx-mavericks
add a comment |
When I try to run previously working git commands, I get this:
dyld: Symbol not found: _sqlite3_intarray_bind
Referenced from: /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
Expected in: /opt/local/lib/libsqlite3.dylib
in /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
git: error: unable to locate xcodebuild, please make sure the path to the Xcode folder is set correctly!
git: error: You can set the path to the Xcode folder using /usr/bin/xcode-select -switch
How can I fix this?
git xcodebuild osx-mavericks
When I try to run previously working git commands, I get this:
dyld: Symbol not found: _sqlite3_intarray_bind
Referenced from: /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
Expected in: /opt/local/lib/libsqlite3.dylib
in /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
git: error: unable to locate xcodebuild, please make sure the path to the Xcode folder is set correctly!
git: error: You can set the path to the Xcode folder using /usr/bin/xcode-select -switch
How can I fix this?
git xcodebuild osx-mavericks
git xcodebuild osx-mavericks
edited Jul 3 '16 at 22:28
Paul
16.7k116397
16.7k116397
asked Oct 29 '13 at 0:53
tol4trobtol4trob
422138
422138
add a comment |
add a comment |
7 Answers
7
active
oldest
votes
This works for me sudo xcode-select --switch /Library/Developer/CommandLineTools/
This works for me!
– Lisa
Oct 25 '15 at 0:27
I had xcode and another xcode beta. After uninstalling the beta I got "Error: Failure while executing: /usr/bin/otool -L /usr/bin/install_name_tool". Then I did this commando and it works again.
– LetsGoRangers
Jun 14 '16 at 8:07
I didsudo xcode-select --switch /Applications/Xcode.app
but that did not solve my problem. Why did your approach solve the problem?
– crisron
Sep 16 '16 at 1:57
Dunno how you figured that out, but it worked for me too.
– Edward Falk
Sep 16 '16 at 5:17
You have to make sure the command line tools are installed, when I finally upgraded to sierra, these weren't installed - osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x
– chrismarx
Nov 23 '16 at 2:31
|
show 1 more comment
After a much googling and confusion, the following steps lead to a solution (with Xcode installed). Some might be optional, so please feel free to elaborate on this as I am not an expert on these errors.
- download mavericks command line tools https://developer.apple.com/downloads/
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
brew install sqlite3
- commented out
DYLD_LIBRARY_PATH
entry in my.bashrc
file
Thanks for these steps.
– abathur
Nov 16 '13 at 18:38
You don't need to download mavericks command line tools/be a developer. You can start on step 2. (assuming you have the new xcode, at least)
– jQwierdy
Dec 8 '13 at 5:58
I'm getting OP's error when trying to install a redmine plugin after updating Command Line Tools to version 6.0 for OSX 10.9. The key takeaway on this was to run the commandsudo xcode-select -switch /Library/Developer/CommandLineTools
which fixed my error. Thanks!
– Kirkland
Sep 30 '14 at 17:44
personally i only needed steps 1-3. thanks for this info!
– gdibble
Nov 5 '15 at 0:03
I only needed step 3
– MikeF
Jan 23 '16 at 23:58
|
show 1 more comment
If you have already installed Xcode, you can run the following command to determine and point to the correct location
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
Or use AppStore to install latest Xcode.
add a comment |
Maybe you should install Xcode 5.0.1 for Mavericks. Check updates.
1
the problem happens with exactly that config on my computer also
– Philip
Oct 31 '13 at 13:45
add a comment |
I hit this same issue running Fastlane on a fresh High Sierra installation.
Solved with:
sudo xcode-select --switch /Applications/Xcode.app
add a comment |
This worked for me, just paste in terminal:
sudo xcode-select --switch /Library/Developer/CommandLineTools/
answer is same as stackoverflow.com/a/31780545/432903
– prayagupd
Nov 20 '18 at 3:14
add a comment |
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
This did it for me.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f19647788%2fgit-error-unable-to-locate-xcodebuild-after-a-fresh-os-x-mavericks-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
This works for me sudo xcode-select --switch /Library/Developer/CommandLineTools/
This works for me!
– Lisa
Oct 25 '15 at 0:27
I had xcode and another xcode beta. After uninstalling the beta I got "Error: Failure while executing: /usr/bin/otool -L /usr/bin/install_name_tool". Then I did this commando and it works again.
– LetsGoRangers
Jun 14 '16 at 8:07
I didsudo xcode-select --switch /Applications/Xcode.app
but that did not solve my problem. Why did your approach solve the problem?
– crisron
Sep 16 '16 at 1:57
Dunno how you figured that out, but it worked for me too.
– Edward Falk
Sep 16 '16 at 5:17
You have to make sure the command line tools are installed, when I finally upgraded to sierra, these weren't installed - osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x
– chrismarx
Nov 23 '16 at 2:31
|
show 1 more comment
This works for me sudo xcode-select --switch /Library/Developer/CommandLineTools/
This works for me!
– Lisa
Oct 25 '15 at 0:27
I had xcode and another xcode beta. After uninstalling the beta I got "Error: Failure while executing: /usr/bin/otool -L /usr/bin/install_name_tool". Then I did this commando and it works again.
– LetsGoRangers
Jun 14 '16 at 8:07
I didsudo xcode-select --switch /Applications/Xcode.app
but that did not solve my problem. Why did your approach solve the problem?
– crisron
Sep 16 '16 at 1:57
Dunno how you figured that out, but it worked for me too.
– Edward Falk
Sep 16 '16 at 5:17
You have to make sure the command line tools are installed, when I finally upgraded to sierra, these weren't installed - osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x
– chrismarx
Nov 23 '16 at 2:31
|
show 1 more comment
This works for me sudo xcode-select --switch /Library/Developer/CommandLineTools/
This works for me sudo xcode-select --switch /Library/Developer/CommandLineTools/
answered Aug 3 '15 at 6:17
sushilprjsushilprj
903716
903716
This works for me!
– Lisa
Oct 25 '15 at 0:27
I had xcode and another xcode beta. After uninstalling the beta I got "Error: Failure while executing: /usr/bin/otool -L /usr/bin/install_name_tool". Then I did this commando and it works again.
– LetsGoRangers
Jun 14 '16 at 8:07
I didsudo xcode-select --switch /Applications/Xcode.app
but that did not solve my problem. Why did your approach solve the problem?
– crisron
Sep 16 '16 at 1:57
Dunno how you figured that out, but it worked for me too.
– Edward Falk
Sep 16 '16 at 5:17
You have to make sure the command line tools are installed, when I finally upgraded to sierra, these weren't installed - osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x
– chrismarx
Nov 23 '16 at 2:31
|
show 1 more comment
This works for me!
– Lisa
Oct 25 '15 at 0:27
I had xcode and another xcode beta. After uninstalling the beta I got "Error: Failure while executing: /usr/bin/otool -L /usr/bin/install_name_tool". Then I did this commando and it works again.
– LetsGoRangers
Jun 14 '16 at 8:07
I didsudo xcode-select --switch /Applications/Xcode.app
but that did not solve my problem. Why did your approach solve the problem?
– crisron
Sep 16 '16 at 1:57
Dunno how you figured that out, but it worked for me too.
– Edward Falk
Sep 16 '16 at 5:17
You have to make sure the command line tools are installed, when I finally upgraded to sierra, these weren't installed - osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x
– chrismarx
Nov 23 '16 at 2:31
This works for me!
– Lisa
Oct 25 '15 at 0:27
This works for me!
– Lisa
Oct 25 '15 at 0:27
I had xcode and another xcode beta. After uninstalling the beta I got "Error: Failure while executing: /usr/bin/otool -L /usr/bin/install_name_tool". Then I did this commando and it works again.
– LetsGoRangers
Jun 14 '16 at 8:07
I had xcode and another xcode beta. After uninstalling the beta I got "Error: Failure while executing: /usr/bin/otool -L /usr/bin/install_name_tool". Then I did this commando and it works again.
– LetsGoRangers
Jun 14 '16 at 8:07
I did
sudo xcode-select --switch /Applications/Xcode.app
but that did not solve my problem. Why did your approach solve the problem?– crisron
Sep 16 '16 at 1:57
I did
sudo xcode-select --switch /Applications/Xcode.app
but that did not solve my problem. Why did your approach solve the problem?– crisron
Sep 16 '16 at 1:57
Dunno how you figured that out, but it worked for me too.
– Edward Falk
Sep 16 '16 at 5:17
Dunno how you figured that out, but it worked for me too.
– Edward Falk
Sep 16 '16 at 5:17
You have to make sure the command line tools are installed, when I finally upgraded to sierra, these weren't installed - osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x
– chrismarx
Nov 23 '16 at 2:31
You have to make sure the command line tools are installed, when I finally upgraded to sierra, these weren't installed - osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x
– chrismarx
Nov 23 '16 at 2:31
|
show 1 more comment
After a much googling and confusion, the following steps lead to a solution (with Xcode installed). Some might be optional, so please feel free to elaborate on this as I am not an expert on these errors.
- download mavericks command line tools https://developer.apple.com/downloads/
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
brew install sqlite3
- commented out
DYLD_LIBRARY_PATH
entry in my.bashrc
file
Thanks for these steps.
– abathur
Nov 16 '13 at 18:38
You don't need to download mavericks command line tools/be a developer. You can start on step 2. (assuming you have the new xcode, at least)
– jQwierdy
Dec 8 '13 at 5:58
I'm getting OP's error when trying to install a redmine plugin after updating Command Line Tools to version 6.0 for OSX 10.9. The key takeaway on this was to run the commandsudo xcode-select -switch /Library/Developer/CommandLineTools
which fixed my error. Thanks!
– Kirkland
Sep 30 '14 at 17:44
personally i only needed steps 1-3. thanks for this info!
– gdibble
Nov 5 '15 at 0:03
I only needed step 3
– MikeF
Jan 23 '16 at 23:58
|
show 1 more comment
After a much googling and confusion, the following steps lead to a solution (with Xcode installed). Some might be optional, so please feel free to elaborate on this as I am not an expert on these errors.
- download mavericks command line tools https://developer.apple.com/downloads/
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
brew install sqlite3
- commented out
DYLD_LIBRARY_PATH
entry in my.bashrc
file
Thanks for these steps.
– abathur
Nov 16 '13 at 18:38
You don't need to download mavericks command line tools/be a developer. You can start on step 2. (assuming you have the new xcode, at least)
– jQwierdy
Dec 8 '13 at 5:58
I'm getting OP's error when trying to install a redmine plugin after updating Command Line Tools to version 6.0 for OSX 10.9. The key takeaway on this was to run the commandsudo xcode-select -switch /Library/Developer/CommandLineTools
which fixed my error. Thanks!
– Kirkland
Sep 30 '14 at 17:44
personally i only needed steps 1-3. thanks for this info!
– gdibble
Nov 5 '15 at 0:03
I only needed step 3
– MikeF
Jan 23 '16 at 23:58
|
show 1 more comment
After a much googling and confusion, the following steps lead to a solution (with Xcode installed). Some might be optional, so please feel free to elaborate on this as I am not an expert on these errors.
- download mavericks command line tools https://developer.apple.com/downloads/
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
brew install sqlite3
- commented out
DYLD_LIBRARY_PATH
entry in my.bashrc
file
After a much googling and confusion, the following steps lead to a solution (with Xcode installed). Some might be optional, so please feel free to elaborate on this as I am not an expert on these errors.
- download mavericks command line tools https://developer.apple.com/downloads/
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
brew install sqlite3
- commented out
DYLD_LIBRARY_PATH
entry in my.bashrc
file
edited Nov 20 '18 at 3:13
prayagupd
20.3k893143
20.3k893143
answered Oct 29 '13 at 13:29
tol4trobtol4trob
422138
422138
Thanks for these steps.
– abathur
Nov 16 '13 at 18:38
You don't need to download mavericks command line tools/be a developer. You can start on step 2. (assuming you have the new xcode, at least)
– jQwierdy
Dec 8 '13 at 5:58
I'm getting OP's error when trying to install a redmine plugin after updating Command Line Tools to version 6.0 for OSX 10.9. The key takeaway on this was to run the commandsudo xcode-select -switch /Library/Developer/CommandLineTools
which fixed my error. Thanks!
– Kirkland
Sep 30 '14 at 17:44
personally i only needed steps 1-3. thanks for this info!
– gdibble
Nov 5 '15 at 0:03
I only needed step 3
– MikeF
Jan 23 '16 at 23:58
|
show 1 more comment
Thanks for these steps.
– abathur
Nov 16 '13 at 18:38
You don't need to download mavericks command line tools/be a developer. You can start on step 2. (assuming you have the new xcode, at least)
– jQwierdy
Dec 8 '13 at 5:58
I'm getting OP's error when trying to install a redmine plugin after updating Command Line Tools to version 6.0 for OSX 10.9. The key takeaway on this was to run the commandsudo xcode-select -switch /Library/Developer/CommandLineTools
which fixed my error. Thanks!
– Kirkland
Sep 30 '14 at 17:44
personally i only needed steps 1-3. thanks for this info!
– gdibble
Nov 5 '15 at 0:03
I only needed step 3
– MikeF
Jan 23 '16 at 23:58
Thanks for these steps.
– abathur
Nov 16 '13 at 18:38
Thanks for these steps.
– abathur
Nov 16 '13 at 18:38
You don't need to download mavericks command line tools/be a developer. You can start on step 2. (assuming you have the new xcode, at least)
– jQwierdy
Dec 8 '13 at 5:58
You don't need to download mavericks command line tools/be a developer. You can start on step 2. (assuming you have the new xcode, at least)
– jQwierdy
Dec 8 '13 at 5:58
I'm getting OP's error when trying to install a redmine plugin after updating Command Line Tools to version 6.0 for OSX 10.9. The key takeaway on this was to run the command
sudo xcode-select -switch /Library/Developer/CommandLineTools
which fixed my error. Thanks!– Kirkland
Sep 30 '14 at 17:44
I'm getting OP's error when trying to install a redmine plugin after updating Command Line Tools to version 6.0 for OSX 10.9. The key takeaway on this was to run the command
sudo xcode-select -switch /Library/Developer/CommandLineTools
which fixed my error. Thanks!– Kirkland
Sep 30 '14 at 17:44
personally i only needed steps 1-3. thanks for this info!
– gdibble
Nov 5 '15 at 0:03
personally i only needed steps 1-3. thanks for this info!
– gdibble
Nov 5 '15 at 0:03
I only needed step 3
– MikeF
Jan 23 '16 at 23:58
I only needed step 3
– MikeF
Jan 23 '16 at 23:58
|
show 1 more comment
If you have already installed Xcode, you can run the following command to determine and point to the correct location
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
Or use AppStore to install latest Xcode.
add a comment |
If you have already installed Xcode, you can run the following command to determine and point to the correct location
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
Or use AppStore to install latest Xcode.
add a comment |
If you have already installed Xcode, you can run the following command to determine and point to the correct location
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
Or use AppStore to install latest Xcode.
If you have already installed Xcode, you can run the following command to determine and point to the correct location
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
Or use AppStore to install latest Xcode.
answered Oct 29 '13 at 3:30
zdkzdk
1,133614
1,133614
add a comment |
add a comment |
Maybe you should install Xcode 5.0.1 for Mavericks. Check updates.
1
the problem happens with exactly that config on my computer also
– Philip
Oct 31 '13 at 13:45
add a comment |
Maybe you should install Xcode 5.0.1 for Mavericks. Check updates.
1
the problem happens with exactly that config on my computer also
– Philip
Oct 31 '13 at 13:45
add a comment |
Maybe you should install Xcode 5.0.1 for Mavericks. Check updates.
Maybe you should install Xcode 5.0.1 for Mavericks. Check updates.
answered Oct 29 '13 at 2:30
tonton
96669
96669
1
the problem happens with exactly that config on my computer also
– Philip
Oct 31 '13 at 13:45
add a comment |
1
the problem happens with exactly that config on my computer also
– Philip
Oct 31 '13 at 13:45
1
1
the problem happens with exactly that config on my computer also
– Philip
Oct 31 '13 at 13:45
the problem happens with exactly that config on my computer also
– Philip
Oct 31 '13 at 13:45
add a comment |
I hit this same issue running Fastlane on a fresh High Sierra installation.
Solved with:
sudo xcode-select --switch /Applications/Xcode.app
add a comment |
I hit this same issue running Fastlane on a fresh High Sierra installation.
Solved with:
sudo xcode-select --switch /Applications/Xcode.app
add a comment |
I hit this same issue running Fastlane on a fresh High Sierra installation.
Solved with:
sudo xcode-select --switch /Applications/Xcode.app
I hit this same issue running Fastlane on a fresh High Sierra installation.
Solved with:
sudo xcode-select --switch /Applications/Xcode.app
edited May 13 '18 at 3:20
Stephen Rauch
30.2k153759
30.2k153759
answered May 13 '18 at 2:58
wantonwanton
737
737
add a comment |
add a comment |
This worked for me, just paste in terminal:
sudo xcode-select --switch /Library/Developer/CommandLineTools/
answer is same as stackoverflow.com/a/31780545/432903
– prayagupd
Nov 20 '18 at 3:14
add a comment |
This worked for me, just paste in terminal:
sudo xcode-select --switch /Library/Developer/CommandLineTools/
answer is same as stackoverflow.com/a/31780545/432903
– prayagupd
Nov 20 '18 at 3:14
add a comment |
This worked for me, just paste in terminal:
sudo xcode-select --switch /Library/Developer/CommandLineTools/
This worked for me, just paste in terminal:
sudo xcode-select --switch /Library/Developer/CommandLineTools/
answered May 21 '18 at 21:24
Kalena GalarnykKalena Galarnyk
11
11
answer is same as stackoverflow.com/a/31780545/432903
– prayagupd
Nov 20 '18 at 3:14
add a comment |
answer is same as stackoverflow.com/a/31780545/432903
– prayagupd
Nov 20 '18 at 3:14
answer is same as stackoverflow.com/a/31780545/432903
– prayagupd
Nov 20 '18 at 3:14
answer is same as stackoverflow.com/a/31780545/432903
– prayagupd
Nov 20 '18 at 3:14
add a comment |
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
This did it for me.
add a comment |
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
This did it for me.
add a comment |
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
This did it for me.
xcode-select --install
sudo xcode-select -switch /Library/Developer/CommandLineTools
This did it for me.
answered Jan 3 at 7:08
aregjanaregjan
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f19647788%2fgit-error-unable-to-locate-xcodebuild-after-a-fresh-os-x-mavericks-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown