Re: dll version collision - my old and now broken solution

2004-05-29 Thread Christopher Faylor
On Sat, May 29, 2004 at 10:27:43AM +0100, Max Bowsher wrote: >Attached is my patch, updated to apply cleanly (though not to work!) >with current CVS. In case it isn't obvious, this patch is just a brute force kludge. Half of the changes aren't even necessary. I'm not sure what the patch buys you

Re: dll version collision - my old and now broken solution

2004-05-29 Thread Baurjan Ismagulov
Hello, Max! Thanks much for the info and the patch, this was much more than I'd expected. I'll try to look at this towards the end of June. With kind regards, Baurjan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Docume

dll version collision - my old and now broken solution

2004-05-29 Thread Max Bowsher
[Sorry not to add to this thread sooner. Exams have been keeping me unavoidably busy.] AFAIK, using multiple independent Cygwin environments simultaneously is impossible without recompiling a modified cygwin1.dll under a different name, and then either recompiling or hex-editing every dll and exe

Re: dll version collision

2004-05-28 Thread Baurjan Ismagulov
Hello, Igor! On Thu, May 27, 2004 at 06:33:20PM -0400, Igor Pechtchanski wrote: > > * It isn't possible with the current cygwin. > It is possible, but non-trivial. Well, I've meant the binary DLL installed using setup. > One way to have Cygwin automatically modify the shared memory area name is

Re: dll version collision

2004-05-28 Thread Baurjan Ismagulov
On Fri, May 28, 2004 at 03:58:09PM -0400, Christopher Faylor wrote: > UML is not linux. It is a mechanism for running linux in userspace. Well, the point was that it can be used for testing. I haven't said it was linux, although for me it more or less is, as long as my kernel module or applicatio

Re: dll version collision

2004-05-28 Thread Christopher Faylor
On Fri, May 28, 2004 at 09:46:34PM +0200, Baurjan Ismagulov wrote: >On Fri, May 28, 2004 at 03:05:50PM -0400, Christopher Faylor wrote: >>You use the same technique as if you were testing another version of >>linux. Or you'd backup your system prior to updating cygwin. It is >>not likely that you

Re: dll version collision

2004-05-28 Thread Baurjan Ismagulov
Hello, Christopher! On Fri, May 28, 2004 at 03:05:50PM -0400, Christopher Faylor wrote: > You use the same technique as if you were testing another version of > linux. Or you'd backup your system prior to updating cygwin. It is not > likely that you could have two installations running on the sa

Re: dll version collision

2004-05-28 Thread Christopher Faylor
On Fri, May 28, 2004 at 01:31:34PM -0400, Michael Hale wrote: >On May 28, 2004, at 1:15 PM, Christopher Faylor wrote: >>On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote: >>>The ideas suggested here are definitely beyond my current ability. I >>>hope someone else who would like this don

Re: dll version collision

2004-05-28 Thread Michael Hale
On May 28, 2004, at 2:17 PM, Reini Urban wrote: Michael Hale schrieb: What is the correct way for someone to run multiple versions of cygwin on their machine then? There's none! That is too bad. I guess that means I will have to worry about varying environments in our build process. At least un

Re: dll version collision

2004-05-28 Thread Reini Urban
Michael Hale schrieb: What is the correct way for someone to run multiple versions of cygwin on their machine then? There's none! > This seems like a very useful feature to me, since among other uses it would allow a new version to be tested along side an older but known version of cygwin. Kill

Re: dll version collision

2004-05-28 Thread Michael Hale
On May 28, 2004, at 1:15 PM, Christopher Faylor wrote: On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote: The ideas suggested here are definitely beyond my current ability. I hope someone else who would like this done, and has the skill will take it up. If it is beyond your abilities t

Re: dll version collision

2004-05-28 Thread Christopher Faylor
On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote: >The ideas suggested here are definitely beyond my current ability. I >hope someone else who would like this done, and has the skill will take >it up. If it is beyond your abilities then you shouldn't be considering this option. Thi

Re: dll version collision

2004-05-28 Thread Michael Hale
The ideas suggested here are definitely beyond my current ability. I hope someone else who would like this done, and has the skill will take it up. On May 27, 2004, at 6:33 PM, Igor Pechtchanski wrote: On Thu, 27 May 2004, Baurjan Ismagulov wrote: Hello, Michael! On Thu, May 27, 2004 at 04:53:1

Re: dll version collision

2004-05-27 Thread Igor Pechtchanski
On Thu, 27 May 2004, Baurjan Ismagulov wrote: > Hello, Michael! > > On Thu, May 27, 2004 at 04:53:17PM -0400, Michael Hale wrote: > > Is it possible to recompile a subset of the cygwin binaries to depend > > on cygwin1.dll renamed to something like build_cygwin1.dll? How would > > I go about doin

Re: dll version collision

2004-05-27 Thread Baurjan Ismagulov
Hello, Michael! On Thu, May 27, 2004 at 04:53:17PM -0400, Michael Hale wrote: > Is it possible to recompile a subset of the cygwin binaries to depend > on cygwin1.dll renamed to something like build_cygwin1.dll? How would > I go about doing this? This is a quite often-discussed topic, but ther

dll version collision

2004-05-27 Thread Michael Hale
Hi, Is it possible to recompile a subset of the cygwin binaries to depend on cygwin1.dll renamed to something like build_cygwin1.dll? How would I go about doing this? The reason that I want to do this is because the developers at our site use the cygwin console for development, and our build p