is there a way to install rev command on mingw, couldn't find it as a package.
I need to use rev on mingw under windows. or do I need to resort to cygwin?
Get it here if you want to execute it from cmd.exe
MSYS doesn't have rev (or I couldn't find where they put it). A full MSYS package (with everything) can be found here. I haven't checked if it's in there or not. If it's not, there is no MSYS "rev".
rev is part of the util-linux package, at least on my Ubuntu system. If MinGW has a util-linux package, you should install that.
Related
I'm trying to install plone 4.3.4 on a SLES 11 SP3 64bit server via the Unified Installer. I've fullfilled all the dependencies listed in the readme.txt, but when I try to get the installer running with the command sudo ./install.sh --password=******* standalone I get the error message: which: no python2.7 in (/usr/bin:/bin:/usr/sbin:/sbin) Unable to find python2.7 on system exec path.
I find that rather strange as in the description of the unified installer it is said "The new Zope/Plone install will use its own copy of Python, and the Python installed by the Unified Installer will not replace your system's copy of Python. You may optionally use your system (or some other) Python, and the Unified Installer will use it without modifying it or your site libraries." on the Plone-Website.
So - what am I doing wrong???
I've just tried adding the parameter --build-python but had to find out that the libxml2-devel and libxslt-devel libraries that are available for SLES-11-SP-3 are sadly not up-to-date enough 2.7.6 instead of 2.7.8 and 1.1.24 instead of 1.1.26 respectively. So no joy there either. :-(
Is there any way to install the current version of plone on SLES 11 SP3 64bit?
Kate
The installer command:
./install.sh standalone --build-python --static-lxml=yes
worked perfectly for me. The installer downloaded and built the Python and libxml2/libxslt components necessary to remedy the terribly out-of-date (and vulnerable) versions included with sles11sp3.
System packages needed for the build were:
gcc-c++
make
readline-devel
libjpeg-devel
zlib-devel
patch
libopenssl-devel
libexpat-devel
man
All installed via zypper.
I'd advise not using sudo for the install. If you want to, you'll need to create the plone_daemon and plone_buildout users and the plone_group group in advance due to oddities in SUSE's adduser implementation.
Using the commandline installer, one can easily install Cygwin with a list of wanted packages like so
setup-x86.exe -q -p='tar,sed,<more packages>'
Is it also possible to fix the version of the packages, something like
setup-x86.exe -q -p='tar:1.2.3,sed,<more packages>'
(this obviously doesn't work)?
The short answer to your query is, No. Cygwin's setup -x86.exe does not give you the flexibility to specify version names along with package names. As per the official doc :
The basic reason for not having a more full-featured package manager is that such a program would need full access to all of Cygwin's POSIX functionality. That is, however, difficult to provide in a Cygwin-free environment, such as exists on first installation. Additionally, Windows does not easily allow overwriting of in-use executables so installing a new version of the Cygwin DLL while a package manager is using the DLL is problematic
There are however a couple of workarounds if you want to download a specific package:
Locate a cygwin mirror that hosts the specific version. Google for your version, and if you find a mirror hosting that version, simply use that mirror before running setup -x86.exe. [source]
Maintain a local pacakge repository and use the commandline options -q -L -l x:\cygwin-local\, where your downloaded package tree is in x:\cygwin-local\ [source] . You can learn how to build and maitain packages here
Compile and install the package after you've set up cygwin using make.
This is function that Cygwin's installer now provides. By default, when running from the command line, it will install the latest version of each package, but you can specify a version with =. For example:
setup-x86_64.exe -P git=2.35.0-1,vim
will install the latest version of Vim, and version 2.35.0-1 of Git.
I am trying to run android ndk-build command in the cygwin terminal.
When I do it is telling me ...
ERROR: Cannot find 'make' program. Please install Cygwin make package
or define the GNUMAKE variable to point to it.
The thing is, I believe I have all the cygwin packages installed. And other topics have suggested running installing and being sure to check the devel>make option as a package. Porblem is, is that there seems to be no make option in the devel package folder.
Does anyone have any insight on this?
NDK comes with its own make, the copy that comes with cygwin has quite a few incompatibilities. You don't need cygwin at all to run the latest versions of NDK (since r6, IIRC). I usually run ndk-build.cmd in a CMD window where cygwin is not on the PATH.
Android's NDK requires both Cygwin and GNU Make. Since I already have the latest & greatest Cygwin installed, I thought that GNU Make must have already been included in it, as Cygwin is pretty developer-oriented.
But I couldn't find any, neither in my local installation, nor in the list of packages, which makes me very curious to understand why, of all GNU packages, this is the one Cygwin chose not to include.
Or perhaps such Cygwin version of GNU make exists and I just couldn't find it?
If so, where/how do I download it?
The make package is GNU make
cygwin.com/packages/make
The GNU version of the 'make' utility
Be sure to install from the Internet, not from "Local Directory":
I just installed Cygwin and can launch a bash shell from windows, do ls, emacs, vi , etc. However, when I do g++ it says command not found.
I thought g++ was installed by default in Cygwin? If that's not the case, what are the exact categories under which I can add g++ as a package to my cygwin?
Did you install the Devel packages?
I would suggest you read this tutorial to get up and running.
It's a good idea to just install everything with CygWin. When you run setup, just click on the circular icon at the top level until it reads "Full" rather then "Default" - that will install all the packages.
I've sometimes had trouble installing single packages due to dependencies but a full install is not affected by that same problem.
Disk space is cheap, your time spent trying to figure out why things don't work is not.