Re: pwd vs $PWD, bash, cygwin vs Linux

Christopher Faylor wrote: In this case, the operative observation is bash != ash. PWD is a bash construct. You would be much better off just using the gnu make "CURDIR" variable. Changing PWD to CURDIR in your examples makes things work as you'd expect. Thanks for the quick response and workarou

Re: pwd vs $PWD, bash, cygwin vs Linux

Christopher Faylor wrote: On Wed, May 04, 2005 at 11:08:43AM +1000, John Williams wrote: Essentially under Cygwin the PWD variable seems to be "frozen" at its value upon first launching Make from the commandline, while under Linux it is being updated for each child process spawned by `m

pwd vs $PWD, bash, cygwin vs Linux

Hello, I am resurrecting a topic that has been discussed before, but there doesn't seem to be a clear resolution (at least not clear to me!). It relates to the behaviour of the PWD variable in the case of multiply nested Makefiles. it was touched upon e.g. here: http://www.mail-archive.com/cy

Re: execvp error:cygwin+make+busybox

Christopher Faylor wrote: On Tue, May 03, 2005 at 10:39:13AM +1000, John Williams wrote: Attempting to cross-compile Busybox 1.00 under Cygwin (1.5.16-1) I am hitting an error similar to one previously reported on the Cygwin list (Jan 05): http://www.cygwin.com/ml/cygwin/2005-01/msg00657.html

execvp error:cygwin+make+busybox

Hello, Attempting to cross-compile Busybox 1.00 under Cygwin (1.5.16-1) I am hitting an error similar to one previously reported on the Cygwin list (Jan 05): http://www.cygwin.com/ml/cygwin/2005-01/msg00657.html No resolution was posted to the list at that time. The busybox Makefile attempts to

Problem with home installation

I have been using cygwin at work for almost a year now and haven't had a single problem with it. Now, I want to work from home on occasion, so I am trying to duplicate my work environment at home. Both machines have Win XP. The installation at home seemed to go just fine, but when I open a cygw

Re: Binary patch tool?

Igor Pechtchanski wrote: Is there a way I can pass these on the command line, without needing a seperate little script file like this? Sure. The easiest for you would probably be vim -b -c ":%s/xygwin1.dll/cygwin1.dll/g|:wq" $f Ain't vim grand? ;-) Indeed. But not just vim, the whole thing. I

Re: Binary patch tool?

Igor Pechtchanski wrote: On Fri, 4 Apr 2003, John Williams wrote: Hi folks, Is there a binary equivalent to the diff/patch combination? I've written a little shell script to run "cmp -b" over a bunch of files (I'm trying to generate binary patches), but now I'm

Binary patch tool?

Hi folks, Is there a binary equivalent to the diff/patch combination? I've written a little shell script to run "cmp -b" over a bunch of files (I'm trying to generate binary patches), but now I'm struggling with a way to actually apply those changes. I started writing a little tcl script to d

Re: Bug in Cygwin bash?

friedman_hill ernest j wrote: I think John Williams wrote: It seems not many people build linux kernels under cygwin - I think if they did, this issue I've found would have been reported earlier, because it's the first step in the kernel configuration process. OK, I've gotta as

Re: Bug in Cygwin bash?

Hi Sam, I've ported uClinux to a new reconfigurable softcore microprocessor. The gcc toolchain for this little beastie runs under Cygwin (well, actually something called Xygwin, but that's another story entirely).. For the record, I've built a couple of bootable kernels under Cygwin. Yes, I

Re: Bug in Cygwin bash?

Randall R Schulz wrote: John, Are you a famous composer? If so, are you _the_ famous composer? No, and nor am I the famous and very talented classical guitarist. I have two guitars, but I can't play either of them :O -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug report

Re: Bug in Cygwin bash?

Randall R Schulz wrote: John, Yes, there's a limitation on the total volume of argument strings. All Unix systems have such a limit and so does Cygwin. The limits vary from system to system, though POSIX dictates a minimum value for this limit. Anybody know the standard Cygwin limit off the top

Bug in Cygwin bash?

Hi folks, I've found a bizarro error that may in fact relate to Cygwin/bash. I'm using the latest version (ran setup and refreshed just yesterday). In the linux kernel configuration process, there is a rule in /linux-2.4.x/makefile that looks like this: dep-files: scripts/mkdep -- `fi

Re: gcc/Cygwin awareness

Hi Max, Max Bowsher wrote: John Williams wrote: Elfyn McBratney wrote: You could use this #if defined(__GNUC__) && defined(__CYGWIN__) So __CYGWIN__ is defined in the preprocessor environment when compiling under Cygwin? That's precisely what I'm after, thanks. General a

Re: gcc/Cygwin awareness

Elfyn McBratney wrote: You could use this #if defined(__GNUC__) && defined(__CYGWIN__) So __CYGWIN__ is defined in the preprocessor environment when compiling under Cygwin? That's precisely what I'm after, thanks. John -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug re

gcc/Cygwin awareness

Hi folks, Is there a macro defined in gcc when running under Cygwin as opposed to, say, linux? I'd like to code something like #ifdef _GCC_UNDER_CYGWIN blah blah #else blah blah #endif This is to get around the fact that Cygwin doesn't provide the libgen.h header file, which I need to build uC

Re: file name case sensitivity

Gerald S. Williams wrote: [snip] But as I said, this is OT for Cygwin. Even if it is added to Cygwin, it will almost certainly not be the default behavior. But for people like me trying to maintain Cygwin versions of Unix projects, it could be a real boon. Indeed. In my case, it would require modi

Re: file name case sensitivity

Shankar Unni wrote: Thorsten Kampe wrote: Yes, but in my opinion it could be of use to John Williams because he wanted to "case sensitivity in filenames under Cygwin". No, it won't work, because if you remember, he said that he had files with the same name but different ca

Re: file name case sensitivity

Hi Elfyn, No. You can use the check_case option in the CYGWIN environment variable, but that'll only get you half way to what you want. Take a look at () to see how it works and how to use it. Thanks for that. As you predict, check_case can't

file name case sensitivity

Hi folks, I see the thread earlier today about this re: gcc - I have a similar question, but not strictly within the context of gcc. I'm building a version of uClinux under Cygwin, and for some reason there are a few places where files exist _in the same directory_ having identical names but d

Re: Obtaining a pervious version

Christopher Faylor wrote: On Wed, Feb 19, 2003 at 11:46:24AM +1000, John Williams wrote: Well a postscript to yesterday's discussion - today I went through all of the Xygwin binary utilities with a hex editor, changed all references of xygwin1.dll -> cygwin1.dll, and blow me down if i

Re: Obtaining a pervious version

Hi again, Well a postscript to yesterday's discussion - today I went through all of the Xygwin binary utilities with a hex editor, changed all references of xygwin1.dll -> cygwin1.dll, and blow me down if it didn't fix the problems! I don't remember who here suggested it, but anyway, it works.

Re: Obtaining a pervious version

Christopher Faylor wrote: The sources available for download are for 1.3.2. The differences are below. Basically, it seems like they made a few changes without really thinking too hard about what they did. So, the cygwin mount table will be found in another registry entry but it will end up in

Re: Obtaining a pervious version

Hey everyone, Thanks all for your input and comments on this thread. If nothing else I've learned a little more about the mechanics of Cygwin, which can't be a bad thing. I have re-assessed my needs and decided I am, in fact, better off running with Cygwin and Xygwin side-by-side, completely

Re: Obtaining a pervious version

Larry Hall (RFK Partners, Inc.) wrote: What doesn't work? The Cygwin provided utilities or the Xygwin1 versions? Neither. I can't run either Cygwin utilities under Xygwin, nor the Xygwin utilities under Cygwin. Full error messages were posted earlier in the thread. I wouldn't necessarily

Re: Obtaining a pervious version

Christopher Faylor wrote: Ok. This version just changes the name of the DLL from cygwin1.dll to xygwin1.dll. What surprises me though is that if I duplicate xygwin1.dll to cygwin1.dll, it doesn't work??? Am I missing something here? Cheers, John -- Unsubscribe info: http://cygwin.c

Re: Obtaining a pervious version

Max Bowsher wrote: John Williams wrote: Max Bowsher wrote: OK, *now* its pretty obvious what the problem is. Cygwin 1.3.20 is backward compatible with Cygwin 1.3.13, but Cygwin is not and never will be sideways compatible with other slightly modified versions of Cygwin. Compile your own EDK

Re: Obtaining a pervious version

Christopher Faylor wrote: On Mon, Feb 17, 2003 at 10:45:20PM -, Max Bowsher wrote: Compile your own EDK toolchain against Cygwin itself, not Xygwin. Correct. I don't suppose you'd be willing to make the "modified" sources available, would you? I'm interested in what these people have do

Re: Obtaining a pervious version

Max Bowsher wrote: OK, *now* its pretty obvious what the problem is. Cygwin 1.3.20 is backward compatible with Cygwin 1.3.13, but Cygwin is not and never will be sideways compatible with other slightly modified versions of Cygwin. Compile your own EDK toolchain against Cygwin itself, not Xygwin.

Re: Obtaining a pervious version

Christopher Faylor wrote: On Mon, Feb 17, 2003 at 10:45:20PM -, Max Bowsher wrote: Compile your own EDK toolchain against Cygwin itself, not Xygwin. Correct. I don't suppose you'd be willing to make the "modified" sources available, would you? I'm interested in what these people have do

Re: Obtaining a pervious version

Max Bowsher wrote: John Williams wrote: They have a cross compiler that uses the cygwin compatability layer. They have modified and distribute a version of this layer, which is built upon cygwin1.dll version 1.3.13. However, they distribute with their tools only a minimal subset of cygwin

Re: Obtaining a pervious version

Christopher Faylor wrote: On Mon, Feb 17, 2003 at 09:55:26AM +1000, John Williams wrote: Hey folks, Two things - first of all, as of 00:00 GMT Cygwin.com appears to be down. Hope it's nothing too serious. Secondly, can you please tell me how to obtain, via the setup installer, a

Obtaining a pervious version

that were built upon Cygwin 1.3.13, and am having versioning issues when trying to run them under 1.3.20. Setup.exe defaults to downloading and installing the most recent distro, but I need to wind back the clock a couple of versions. Is there a simple way to do this? Thanks, John -- Dr Joh