Just installed Yosemite and when I run brew doctor I get:
Warning: Your Xcode (6.0.1) is outdated
Please update to Xcode 6.1.
Xcode can be updated from the App Store.
But in the AppStore it looks like XCode 6.0.1 is the latest version. What's the best way to correct this?
Tis that slight lag between 10.10 being Avail and xcode getting updated. If you read the top of brew doctor output it says
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
So if everything is working, then you should do what it suggests and ignore it. The command line tools / compilers where updated for 10.10 (software update should have picked them up for you). Are you running into any issues with compiling? or just that warning.
pulling up from the comments. Your ruby and postgresql issues are from the upgrade, but it isn't really brews fault, or that compiler error warning.
with rvm just reinstall your ruby. My main dev is done with ruby-2.1.3 so
rvm reinstall ruby-2.1.3
rebuilt ruby and all my gems. The problem is that the ssl libs (maybe others) that ruby was linked to were removed / replaced in the upgrade to 10.10. The reinstall will rebuild and relink to the newer correct libs.
postgresql is slightly different. Apparently during the upgrade a couple of empty directories in /usr/local/var/postgres get removed. No idea why.
see this SO answer for how to fix that.
`pg_tblspc` missing after installation of latest version of OS X (Yosemite or El Capitan)
also if you are use pow (http://pow.cx) you will need to upgrade it to the latest version as 10.10 removed ipfw completely and only leaves pf as the firewall. so you will need to the new version which uses pf anchors.
The above steps where all I needed to do it in order to get my dev back to working.
Looks like developer.apple.com does show an XCode 6.1 as "Available Shortly" as of Fri, Oct 17, at 10pm central time. Not yet available from the AppStore. I guess I'm just too eager for an update.
Related
I'm asking that because I was using Bigsur 2 days ago and no available version is currently working with Bigsur, so I downgraded my os to El capitan and I tested all options but no one is working. Today I am using Mojave 10.14.6 and still no version available.. Do you know a mac os version is working fine with valgrind please ? Thank's !
MacOS 10.13 is the last supported in the official git repo.
You should be able to get 10.14 to work with an unofficial clone (look for Louis Brunner on GitHub, there should be a brew recipe as well).
The poor state of affairs is all down to lack of resources. The Valgrind dev team has a fairly high bar to become a submitter. No-one is actively working on macOS. If people want Valgrind on macOS then we (the Valgrind dev team) need someone to step up and make a long term commitment to working on it.
Finally, there is also a significant possibility that macOS will be removed entirely from the official Valgrind repo. This was discussed as a possibility for 3.19. The subject hasn’t been raised for the next release (3.20 due out next month, October 2022).
I am unable to successfully utilize the pdf-tools package.
Environment:
macOS Monterey 12.0.1
Emacs 27.2
To the best of my understanding, I have followed the installation instructions as outline on https://github.com/politza/pdf-tools:
I've installed and confirmed that the installations of poppler and automake are up-to-date
Though it doesn't seem to be required for the MacOS install, I've installed and confirmed that the installations of gcc and glib are up-to-date.
I've set the PKG_CONFIG_PATH in the init.el file using setenv and confirmed its settings using getenv
(setenv "PKG_CONFIG_PATH" "/usr/local/Cellar/zlib/1.2.8/lib/pkgconfig:/usr/local/lib/pkgconfig:/opt/X11/lib/pkgconfig")
When I try to execute pdf-tools-install and select y in response to the question "Need to (re)build the epdfinfo program, do it now?" I get a compilation error which reads:
mode: compilation; default-directory: "~/.emacs.d/elpa/pdf-tools-20211110.513/build/server/"
Comint started at Thu Dec 2 09:17:05
/Users/username/.emacs.d/elpa/pdf-tools-20211110.513/build/server/autobuild -i /Users/username/.emacs.d/elpa/pdf-tools-20211110.513/
Failed to recognize this system, trying to continue.
Configuring and compiling
No such program: autoreconf
Comint exited abnormally with code 1 at Thu Dec 2 09:17:05
I have confirmed that the referenced directory exits and that autoreconf is installed and up-to-date.
For a long while, I had a working pdf-tools setup on my Mac (thank you Andreas Politz and all the other contributors for such a fabulous tool). Suddenly, I don´t really know how or why, it stopped working. I also deleted my homebrew HEAD version of pdf-tools, which made things worse, because I have never again managed to install pdf-tools from Homebrew.
I tried many tweaks, until, finally, I believe the trick that really got things running again was setting the PKG_CONFIG_PATH to everything that mattered inside the init.el file (and downloading XQuartz to get a X11 environment, with the only purpose of having renderproto in the system; it may have been available in an easier way, but it was only like this that I managed to do it).
Here are all the key steps involved in getting pdf-tools back to work in my MacOS Monterey 12.5 running Emacs 28.1 :-)
Download and install XQuartz to get X11 in your Mac (this might be unnecessary, but it helped me).
In case you haven't already, install other dependencies through homebrew:
brew install poppler automake pkg-config
Through M-x list-packages, install pdf-tools.
In your init.el file, set the PKG_CONFIG_PATH using setenv:
(setenv "PKG_CONFIG_PATH" "/usr/local/Cellar/zlib/1.2.12/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/X11/lib/pkgconfig:/usr/local/Cellar/poppler/22.06.0_1/lib/pkgconfig:/opt/x11/share/pkgconfig")
Of course, you will have to use your own version numbers and update them every time you upgrade zlib and poppler. (zlib now ships with mac OS. If like me you're on mac OS 12.6 or later--and most probably even earlier--you can use /usr/local/opt/zlib/lib/pkgconfig:, which won't have to be updated manually).
Personally, I did all this through the use-package configuration macro that helps organize the init.el file:
(use-package pdf-tools
:ensure t
:config
(setenv "PKG_CONFIG_PATH" "/usr/local/Cellar/zlib/1.2.12/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/X11/lib/pkgconfig:/usr/local/Cellar/poppler/22.06.0_1/lib/pkgconfig:/opt/x11/share/pkgconfig")
(pdf-tools-install)
(custom-set-variables
'(pdf-tools-handle-upgrades t)))
Close Emacs and and re open it in the Terminal and, type y when prompted to "(re)build the epdfinfo program". (For some reason, rebuilding the epdfinfo program seems to work better in the Terminal than in the GUI version of Emacs).
That's all it should take to get pdf-tools to work. It did for me, anyway.
try installing the package 'autoconf' the same way you installed 'automake'.
I am currently working from Mono Version 3.2.8 and am running into trouble finding any documentation on this version. I have no idea what code will run until after I get the exceptions. Either a compatibility list to what works or an idea of what version I can compile that works would be great. Any one have experience with this?
You can manually install the latest version. I was easily able to install
Mono version 4.6.2 on Raspbian.
The http://www.mono-project.com/docs/ site gives a general answer for which major libraries work. Letting you know when there isn't full compatibility but doesn't give specifics.
I used RailsInstaller (for Windows) to set up my environment for my Rails 3 app. I recently installed Pik so that I can update my ruby version as well.
According to the Pik docs https://github.com/vertiginous/pik/wiki/Usage, running 'pik install ruby 1.9.3' should install lastest version of ruby (or atleast the latest patch level for the version I am specifying).
However, this only installs ruby 1.9.3p429, but I understand that 1.9.3p545 is available.
Does anyone know how I can install 1.9.3p545?
Thanks!
Looks like you went with Pik from your previous question. I read on another thread that Pik only supports some of the 1.9.3 patch levels, but unfortunately nothing verifiable. The project has also been abandoned, no longer maintained, which might explain why that latest patch isn't supported...
Might just be my perspective, but seems like Windows is very poorly supported in the Rails/Ruby world? Our project requires Windows and Linux support which is causing us lots of grief. If you find a solid & reliable upgrade solution for Windows I would be very interested!
So I have some Objective-c code that was created in Xcode 3.1 on OSX 10.5.8, and it will no run in Xcode 4. I used this handy little guide http://hints.macworld.com/article.php?story=20110318050811544 on one of my 10.7.4 box and it worked swimmingly. (I had just upgraded from 10.6).
So now I am trying to do the same, install 3.2, install 4, link SDKs etc on another machine running 10.7.3, and after using the little date hack with the same 3.2 mpkg that i used on the other computer, the installer says it finishes successfully but when I go to look, Xcode isn't installed anywhere, and the directory mentioned in the instructions linked above /Developers/SDKs doesn't even exist (it did on the other computer). I tried copying the 10.5 SDK from the 10.7.4 machine to the 10.7.3 machine and still nothing, 4 won't run it, and I get this error.
ld: cannot link directly with /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk/usr/lib/libcrypto.0.9.7.dylib for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
A little history too, the 10.7.4 machine had xcode 3 installed on it previous to it's update to lion so that was already there and I didn't have to mess with any of that nonsense. Is it something with having had it installed previous to the Lion upgrade?
So, how do I get Xcode 3 to work on the machine, and second does anyone recognize that error?
I think mean Xcode 4 does run, but can't build your project since that error message is from the linker at the last stage of building your project.
Here's a much easier way to install Xcode 3 on Lion: http://anatomicwax.tumblr.com/post/8064949186/installing-xcode-3-2-6-on-lion-redux
Make sure you install it to a different folder named other than Developer. Xcode 4 may go out of its way to find /Developer and remove it. I named mine /Xcode3.