I followed several tutorials-which all appeared to say the same thing-on how to create deployable flat-packages (.pkg) using the OS X system provided pkgbuild tool. The packages was always generated just fine. They did, however, not want to be installed.
Running the graphical Apple Installer or the command line interface installer aborted the installation early on giving an generic “Unknown error” after prompting for higher permissions.
Hours later after closer investigation I discovered that I could not install other packages either. Not even updates and new installations from the OS X App Store. Why could I not install my own nor any other packages? What was going on?
The installer daemon service itself is unresponsive. Force quit the installed program from from the Activity Monitor, or from the command line with sudo killall installd.
Related
The other day, I have installed the latest updates through the OS X app store. Today, I can no longer start Eclipse. Basically the loading hangs somewhere in the splash screen. I can open an empty workspace, but when trying to open my usual workspace, it hangs.
I am using Eclipse Neon and work on OS X El Capitan.
If latest updates in the app store included an XCode update (which is the case here), then make sure you run XCode once before running Eclipse, so that you can accept the terms of use. Apparently, the Eclipse GIT plugin has some dependency on XCode.
I discovered this by looking at the log file in the Eclipse workspace which contained lines like this:
2016-09-22 08:17:45,781 [Thread-5] ERROR org.eclipse.jgit.util.FS -
Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.
When I run xcode-select --install in the Terminal, I get the prompt to install the Developer Tools as desired (and as described in this post). But when I run the installation, the process stops at around 50% with a message along the lines of:
Could not install the software because the update server cannot be reached.
My internet connection works fine and I do not think that Apple's servers can be down for more than a couple of hours so I looked at the Console. This is what I found there:
23.02.14 23:25:38,513 mds[63]: (Normal) Volume: volume:0x7fdb79016000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Recovery HD
23.02.14 23:25:38,538 fseventsd[73]: Logging disabled completely for device:1: /Volumes/Recovery HD
23.02.14 23:25:38,000 kernel[0]: hfs: unmount initiated on Recovery HD on device disk0s3
Next I tried to install the Developer Tools from http://developer.apple.com/downloads/ and the installer said the installation was successful. Except that the Developer Tools still don't work.
xcode-select -p
returns
/Applications/Xcode.app/Contents/Developer
What is the issue here?
UPDATE
It looks like the .dmg install from http://developer.apple.com/downloads/ was actually successful. The reason I wanted to install the Deveolper Tools in the first place was because I wanted to install the Python Imaging Library with PIP but failed and read somewhere that this was due to the lack of the Command Line Developer Tools. I found a solution to this problem here. The question of my thread is not really resolved though (why the misleading message when I try to install the Developer Tools?) which is why I do not mark the question as answered for now.
I recently got a used Mac with Mountain Lion on it. I don't know of the admin password or anything, but I do know how to run a command line.
So here's what I am stuck on:
When I click install, it asks me for my username and password (which I don't know).
I want to install this via single-user mode (Cmd+S on Startup), which I accepted the license using it.
Do you guys know how I could achieve this?
At least on Xcode 9.2, you could use:
sudo xcodebuild -runFirstLaunch
to accept the agreement and install additional components.
Resolved this issue using the below commands, it is on OS El Capitan and Xcode beta 7.2
sudo /Applications/Xcode-beta.app/Contents/Developer/usr/bin/xcodebuild -license accept
sudo installer -pkg /Applications/Xcode-beta.app/Contents/Resources/Packages/MobileDevice.pkg -target /
sudo installer -pkg /Applications/Xcode-beta.app/Contents/Resources/Packages/MobileDeviceDevelopment.pkg -target /
Change the Xcode-beta.app path to your own, and you would need sudo(admin) access. Close your Xcode and open again.
I know this is a looooooong time after the original post, but just in case anyone else finds this (as I did) while trying to install Xcode 8.2.1 on El Capitan (10.11.6)…
I had all the same problems listed here – long delay for launch, then asking for additional tools to be installed, only to fail. The command line tools install also failed. I tried the various command line solutions listed, but none worked.
However, upon checking the log I saw that I was getting errors with certificates. On a hunch, I decided to put the system clock back to 20 December 2016 - voila, installs work like magic.
Put the clock back to today (30 October 2019) and still seems to work.
The commandline way to install required components is:
/Applications/Xcode.app/Contents/MacOS/Xcode -installComponents
Here's what I ended up doing.
I went into recovery mode (CMD+R on startup), then to Terminal. I typed in
resetpassword
which then brought up a dialog of where I can select the user and set the password.
I then set the root password. Now when I can enter an admin password, I type in "root" and the password I set.
I got Xcode to load finally!
Xcode 5.1.1 have a new argument:
> xcode -installComponents
I understand that starting with Xcode 4.3 the CLI tools are a separate installation and that caused many issues with existing MacPorts installations upon upgrade. This question is not about that problem. With a brand new rMBP 15.4", I attempted to install only the CLI tools via download from the Apple Developer site. Not only did MacPorts fail to find Xcode, but xcodebuilder itself failed to execute (simply hangs...). I tried many iterations of using xcode-select to point to the CLI binaries, but I couldn't get either MacPorts or just the CLI binaries to work.
Is it simply not possible to only install (the wonderfully tidy and SSD-friendly) CLI tools and get MacPorts to work? I was not able to find anybody that specifically confirmed or denied this in several searches here and on Google in general. With a 128GB SSD, every GB counts... and the 4+GB Xcode install (99% of which I don't need) is a waste of space. Is there something in the proper Xcode install that MacPorts requires?
I have tried many times to install Mono, using the current and beta builds. Every time I install it, it says that it's successful, but I go to the /Library/Frameworks folder and Mono just isn't there. I ran the uninstall script, but it said that permission was denied. I even tried turning on AppleShowAllFiles, and it still wasn't there. I am running OSX Lion.
-rulla101
Check under /Users/_your_name_/Library/Frameworks
Regarding "permissions denied" try running the script with sudo command with terminal.