RE: Building core cygwin packages which only come with patch files over gnu.org packages

By the way, when I try to build it says Automake 1.10a is required. However, this version isn't an option under cygwin, only 1.10.3, 1.10.2, etc. How do I fixed this, hack configure.ac? -Original Message- From: neil.mowb...@calgacus.com [mailto:neil.mowb...@calgacus.com] Sent: 03 January

RE: Building core cygwin packages which only come with patch files over gnu.org packages

Okay, so I get the general idea. First you get the cygwin-src package. Unpack it and run cygport on the coreutils-7.0-2.cygport file with download option. This downloads the original gnu package and applies the two patch files. coreutils-7.0-2.src.patch and coreutils-7.0-2.cygwin.patch. I assume

Building core cygwin packages which only come with patch files over gnu.org packages

Folks, Of course I can try to figure it out myself, but I wonder if anyone can give me a quick pointer on how to build core cygwin packages which only provide patch files over the orginal GNU source. For eample coreutils-7.0-2-src.tar.bz contains: coreutils-7.0-2.cygport coreutils-7.0-2.cygport

Missing #defines from cygwin

Folks, At least the following are missing from cygwin's #define FILE_ATTRIBUTE_VIRTUAL 0x0001 (from MS WinNT.h) #define SYMBOLIC_LINK_FLAG_DIRECTORY(0x1) (from MS WinBase.h) Regards, Neil -- Problem reports: http://cygwin.com/problems.html

RE: /var/lib/alternatives/gcc missing for alternatives 1.3.30c

Thanks folks. I did have a /etc/postinstll/gcc.sh.done but it was installing v3.0 so I modified to v4.0 and run it which solved the problem. Also apologies for not understanding how alternatives works -- all fixed now. Regards, Neil Larry Hall (Cygwin) wrote: > On 12/30/2009 08:07 AM, neil.mowb

Appropriate expectation on the degree of cygwin and MS interoperability

Folks, A bit of a vague question but any greater clarity concerning the appropriate level of interoperability between Cygwin and MS would be appreciated. I have my Windows 6 and 7 platforms configured to build software using different toolchains, the most common being (1) Visual Studio 10 and (2)

Using cygwin headers/libraries in MS compiled programs

Folks, Apologies for the dumb question and please re-direct if there is a better forum. How do I use cygwin *.h and *.dll in MS console programs? If I include in a MS program I get many conflicts between the cygwin CRT and MS CRT stuff. Is my only options to "port" the headers to MS and dynam

RE: Bash v4.0 does not respect $PATH

Sorry I missing the last question. To answer it: yes perl really is visible as /opt/perl/bin/perl which bash fails to execute it as the third line below shows. In this shell bash execute cygwin perl on line 5. ls: cannot access /opt/site/bin/perl: No such file or directory ls: cannot access /opt

RE: Bash v4.0 does not respect $PATH

As requested the output from perl -e "print $^X;" Bash 3 => c:\opt\perl\bin\perl.exe Bash 4 => /usr/bin/perl As you would expect the program that is actually running. But again Bash 4 is incorrectly getting /usr/bin/perl rather than /opt/perl/bin/perl -Original Message- From: Csaba Radu

RE: Bash v4.0 does not respect $PATH

Yes I'm certain. Below is a log of the following script #--- script $ echo "bash version = ${BASH_VERSINFO[0]}" $ for i in $(echo $PATH | sed -r -e "s/:/ /g"); do echo $i; done $ which perl $ perl --version $ /bin/bash $ echo "bash version = ${BASH_VERSINFO[0]}" $ for i in $(echo $P

/var/lib/alternatives/gcc missing for alternatives 1.3.30c

Dear Folks, The scripts /bin/set-gcc-default-[34].sh are written to use alternatives to install gcc-3 and gcc-4. But /var/lib/alternatives/gcc is missing. I tried to create it using g++ as an example but all functions failed with an error failed to read link /usr/bin/gcc.exe (which is the orgina

Bash v4.0 does not respect $PATH

Folks, I need associative arrays so I got the bash 4.0 source, compiled it under cygwin and installed it in /usr/local/bin. I have ActiveState perl installed in /opt/perl which preceeds /usr/local/bin:/bin:/usr/bin on my path. Using bash 4.0, 'which' says I should get ActiveState perl, but actua