Hello.
I am wondering why installing VIm installs so many other things: After doing a
default install of Cgwin, and then not finding VIm, I added VIM to the install
as well, but found it greatly increased my Cygwin install as follows.
Dependencies listed to be installed:
crypt
libdb4.5
libgb
On Fri, May 3, 2013 at 4:08 AM, Jan Nijtmans wrote:
> 2013/5/3 Kai Tietz:
>> 2013/5/3 Jan Nijtmans wrote:
>>> The mingw-w64 cross-compiler in Cygwin64 (x64_64-w64-mingw32)
>>> is currently lacking "errno.h",
>> Absoultely an absurdity. Of course mingw-w64 provides an errno.h
>> header. Not sure
Thanks for the solution, this fixed the same problem I encountered after
installing X11.
Andrey Repin-3 wrote
> Greetings, All!
>
> I was installing ImageMagick for first time, and Setup.exe hit the
> abovementioned error.
> Setup.log.full contains these relevant lines:
>
> 2013/02/16 21:31:27
On 2013-05-07 15:40, Daniel R. Grayson wrote:
Thank you. Your output shows that the dependency of git upon libsasl2
is indirect, and that the real problem is that the package
libopenldap2_4_2 fails to list libsasl2 as a dependency, even though
its dll depends on it:
$ cygcheck /bin/cygldap-2-4-
On 4/29/2013 10:50 PM, Arthur Tu wrote:
On 4/30/2013 12:47 AM, Ken Brown wrote:
On 4/28/2013 12:56 PM, Arthur Tu wrote:
After lualatex command, file
"~/.cache/texmf/luatex-cache/generic/names/otfl-names.lua" was
generated.
Entry like this for example
{
["familyname"]="SimSun",
["fil
Thank you. Your output shows that the dependency of git upon libsasl2
is indirect, and that the real problem is that the package
libopenldap2_4_2 fails to list libsasl2 as a dependency, even though
its dll depends on it:
$ cygcheck /bin/cygldap-2-4-2.dll | grep sasl
C:\cygwin\bin\cygsasl2-2.dll
Hi all,
Running the attached STC inside gdb hangs (zero CPU util, have to kill
gdb from Task Manager, killing a.exe doesn't cut it).
Compile line used: g++ -Wall -g -mthreads -DBUG bug.cpp
I currently have the following package versions:
cygwin-1.7.18(0.263/5/3) 2013-04-19
mintty-1.1.3-1
gdb-
Le 7 mai 2013 à 16:39, Warren Young a écrit :
> Your script will also fail on most FreeBSD machines, for example. On
> FreeBSD, there is a kernel build option that is often set which prevents user
> space from *ever* seeing command line options. It's a security feature,
> since there are all
On 5/7/2013 02:46, AZ 9901 wrote:
This script uses "ps -ef" in particular to list all its instances.
Any script that relies on 'ps' output parsing is probably unportable
from the get-go.
Your script will also fail on most FreeBSD machines, for example. On
FreeBSD, there is a kernel build
Le 7 mai 2013 à 10:46, AZ 9901 a écrit :
> Hello,
>
> I run a bash script in a multi-user environment.
> This script uses "ps -ef" in particular to list all its instances.
>
> On a common UNIX / Linux system, it gives something like this :
> bobby 20326 20318 0 10:21 ?00:00:00 /bin/
Hello,
I run a bash script in a multi-user environment.
This script uses "ps -ef" in particular to list all its instances.
On a common UNIX / Linux system, it gives something like this :
bobby 20326 20318 0 10:21 ?00:00:00 /bin/bash ./myscript.sh
marty 20330 20342 0 10:23 ?
11 matches
Mail list logo