The RCS, like ci, co, rlog, etc. can find in Xcode 5.0(with command line developer tool) in mountain lion, but disappear in mavericks with xcode 5.0.1(with command line developer tool).
Is apple abandoned the simple version control tool?
From Xcode release notes:
The CVS and RCS source control tools have been removed from Xcode 5. 11968433
Here's what I did:
Used a time machine backup to restore ci, co, rcs, rcsclean,
*rcsdiff, rcsmerge, and rlog* to my directory ~/bin/rcs
Unfortunately, the system needs to find them in /usr/bin. I did not
want to add new files to that directory. So I reluctantly (via terminal and sudo) typed
ln -s ~/bin/rcs/* /usr/bin
If you don't want to recompile from source, Rudix is probably the simplest way to install RCS.
The latest version installs in /usr/local/bin and run well in Mavericks. You might want to symlink it in /usr/bin afterward.
Related
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'.
http://zzsethzz.blogspot.de/2013/02/install-chromium-upgrade-it-to-chrome.html
According this tutorial, I should remove all HDDs I do not want to install chromium OS to during install. I wanted to try this guide on my imac using an external SSD for chromeos. Obviously, removing the HDD isn't an option. Will the chromiumOS installer format my mac drive too, if I don't remove it?
AS the writer of that tutorial I can hopefully help you. When you install Chromium OS to begin with you can specify where to install to if you know your unix commands well enough. and then from there you can update to Chrome OS once you have your external working for you.
To find out what your hard drive is when connected, open a terminal (you may need to use a developer terminal) and use the command "fdisk -l" This will list your hard drives. for example /dev/sda1 etc...
Your install command would be "Install /Dev/sda1" but replace the dev part with whatever your hard drive was listed as. If you need further help email me at admin#xiaorishu.co.uk
Possible?
I think to do this I need to upgrade the AIR runtime on the Fire to 3, but the version in the app store won't install. I can't create an AIR apk that is both captive runtime and debug that I know of, so the debug version of the app has to run on the AIR runtime installed. Since the Fire comes with 2.7, 3.x apps won't run in debug mode.
Has anyone managed to get AIR 3 running on a Fire without using captive runtime?
To update AIR on your KF you have to get root privileges. Also keep in mind that android build on KF doesn't have any copy command (it cut off). So the best way I found is to flash your KF with modified (pre-rooted) stock version and then install new air.
Get pre-rooted stock version (I took it here). IMPORTANT: it installs via TWRP, google how to install TWRP on KF.
Put downloaded .zip and air_runtime.apk (latest AIR version) in the root of KF.
Reboot in Recovery mode (TWRP should load)
Flash this version.
On your PC open cmd and run "adb shell" (make sure you see your device in list when run "adb devices" otherwise check drivers).
Run "su" (if you downloaded secure version).
In shell go to sdcard ("ls" to get list of files/folders and "cd folder_name" to get into) and run "install air_runtime.apk /system/app/air_runtime.apk" (I think you can just run "install /sdcard/folder_with_air/air_runtime.apk /system/app/air_runtime.apk").
(7a. If it tells you that can't install because of file already exist, run the following two commands: "mount -o remount rw /system" (mount 'system' with read/write rights) and "mv /system/app/air_runtime.apk /system/app/air_runtime.bak" (rename air_runtime.apk into air_runtime.bak). Then repeat step 7.)
In KF just run (install) air_runtime.apk (use any file explorer, e.g. download ES File Explorer from Amazon).
Check AIR version in Applications.
That's all. Looks a bit complex, but in real it takes about 4-5 mins for me to update AIR (BUT I have TWRP already installed).
Hope it helps.
UPD. After your Kindle updates itself (version 6.3.1 currently the latest) you'll lose you SU privileges. AIR also will be rolled back to 2.7. You can prevent KF auto-updates (search on xda how to do it) or flash actual pre-rooted version (it gives you several months without problems).
I installed the Xcode Snow Leopard beta in my Developer folder, but I decided to re-intall Xcode 4.0.2. So I deleted the Developer folder, and ran the installer.
Now when I try to open Xcode it just bounces a few times in the Dock, but doesn't launch.
Do I need to delete some other files to get it working?
Go to terminal and run this:
$ sudo /Developer/Library/uninstall-devtools --mode=all
After that finishes running, delete the /Developer directory again and reboot your computer (you must reboot your computer). When it comes back, re-install Xcode and you should be fine.
The problem is as follows: I have a MonoDevelop project (ASP.NET) on my development workstation.
I'm currently at a customer site, without my regular development environment on my laptop (Regulatory Burden). I have SSH access to my development workstation, but the network is too laggy to handle X11 comfortably.
I need to make a minor adjustment and recompile. I tried using xbuild, with no effect:
qdot#trigati ~/svn/proj/trunk/proj $ xbuild proj.csproj
XBuild Engine Version 2.6.4.0
Mono, Version 2.6.4.0
Copyright (C) Marek Sieradzki 2005-2008, Novell 2008-2009.
MSBUILD: error MSBUILD0000: /home/qdot/svn/proj/trunk/proj/proj.csproj: Imported project:
"/usr/lib/mono/xbuild/Microsoft/VisualStudio/v8.0/WebApplications/Microsoft.WebApplication.targets" does not exist.
Is there some utility that can trigger a rebuild of the monodevelop sourcecode? Obviously the code builds through the GUI.
mdtool build proj.csproj
If you want to use xbuild, create a symlink:
cd /usr/lib/mono/xbuild/Microsoft/VisualStudio/v9.0
ln -s v9.0 v10.0
I have the same exact ubuntu 12.04 distro on two different computers and could not figure out why mono would compile on one computer and not the other. But oh well, symlink solved the problem.