On Wed, Mar 30, 2005 at 09:31:50AM +0200, Corinna Vinschen wrote:
The idea of a third party packager's guide sounds good to me. I'd
rather have third parties not to pack Cygwin in their packages at all
and to point the user to install Cygwin from cygwin.com instead, but I
guess that's rather
Christopher Faylor wrote:
OTOH, perhaps I'm oversimplifying things, but it seems like this thread
went on for quite a while after the simple delete the nonstandard DLL
advice was given. I don't see how any advice is going to be useful if
it isn't followed.
I agree completely. All the more reason
On Wed, Mar 30, 2005 at 08:08:16AM -0800, Jim Kleckner wrote:
Christopher Faylor wrote:
OTOH, perhaps I'm oversimplifying things, but it seems like this thread
went on for quite a while after the simple delete the nonstandard DLL
advice was given. I don't see how any advice is going to be useful
Christopher Faylor wrote:
On Wed, Mar 30, 2005 at 08:08:16AM -0800, Jim Kleckner wrote:
Christopher Faylor wrote:
OTOH, perhaps I'm oversimplifying things, but it seems like this thread
went on for quite a while after the simple delete the nonstandard DLL
advice was given. I don't see how any
On Wed, Mar 30, 2005 at 08:45:10AM -0800, Jim Kleckner wrote:
Christopher Faylor wrote:
On Wed, Mar 30, 2005 at 08:08:16AM -0800, Jim Kleckner wrote:
Christopher Faylor wrote:
OTOH, perhaps I'm oversimplifying things, but it seems like this thread
went on for quite a while after the simple
Christopher Faylor wrote:
On Wed, Mar 30, 2005 at 08:45:10AM -0800, Jim Kleckner wrote:
So, if you're a Unix guy since 1978, that puts you in a unique category.
You don't qualify as a FAQ.
I don't quite understand this. I don't qualify to write FAQ entries
or shouldn't be allowed to use them?
I
On Wed, Mar 30, 2005 at 09:57:44AM -0800, Jim Kleckner wrote:
Christopher Faylor wrote:
On Wed, Mar 30, 2005 at 08:45:10AM -0800, Jim Kleckner wrote:
So, if you're a Unix guy since 1978, that puts you in a unique category.
You don't qualify as a FAQ.
I don't quite understand this. I don't
Christopher Faylor wrote:
On Wed, Mar 30, 2005 at 09:57:44AM -0800, Jim Kleckner wrote:
Then strike the link text and limit it to the workaround of adding
the bin to the system path. My text was a suggested starting point.
i.e., a workaround.
The solution that the DLL has to be in the system
On Wed, Mar 30, 2005 at 11:20:16AM -0800, Jim Kleckner wrote:
Christopher Faylor wrote:
On Wed, Mar 30, 2005 at 09:57:44AM -0800, Jim Kleckner wrote:
Then strike the link text and limit it to the workaround of adding
the bin to the system path. My text was a suggested starting point.
i.e., a
Larry Hall wrote:
At 10:20 PM 3/24/2005, Brian Dessent wrote:
A symlink won't work, because it's Windows own loader that searches
for and loads any .DLLs called for by an .exe. Windows does not
understand symlinks as they are a Cygwin thing, so you can't
symlink a DLL and expect it to load.
At 05:49 PM 3/29/2005, you wrote:
Larry Hall wrote:
At 10:20 PM 3/24/2005, Brian Dessent wrote:
A symlink won't work, because it's Windows own loader that searches
for and loads any .DLLs called for by an .exe. Windows does not
understand symlinks as they are a Cygwin thing, so you can't
On Mar 29 22:55, Larry Hall wrote:
At 05:49 PM 3/29/2005, you wrote:
If there is interest, I am willing to take a crack at pulling
together the information that is sprinkled in email threads
about how to avoid trampling on existing cygwin installations.
Eventually, there really should be a
On Thu, Mar 24, 2005 at 10:50:07AM -0800, Jim Kleckner wrote:
I had a user install clamwin and as discussed on the list here:
http://www.cygwin.com/ml/cygwin-apps/2004-09/msg00288.html it blithely
installs cygwin1.dll regardless of any installation of cygwin. This
predictably causes problems.
At 01:50 PM 3/24/2005, you wrote:
I had a user install clamwin and as discussed on the list here:
http://www.cygwin.com/ml/cygwin-apps/2004-09/msg00288.html
it blithely installs cygwin1.dll regardless of any installation
of cygwin. This predictably causes problems.
Searching through the user
Larry Hall wrote:
At 01:50 PM 3/24/2005, you wrote:
I had a user install clamwin and as discussed on the list here:
http://www.cygwin.com/ml/cygwin-apps/2004-09/msg00288.html
it blithely installs cygwin1.dll regardless of any installation
of cygwin. This predictably causes problems.
Searching
Jim Kleckner wrote:
This is helpful, thank you. Being curious and trying to be minimal
about changes to the system in question, I tried removing and linking
the dll in place. I first tried ln -s /bin/cygwin1.dll in the
clamwin/bin directory and wasn't surprised that it didn't work.
Being Unix
On Thu, Mar 24, 2005 at 06:13:55PM -0800, Jim Kleckner wrote:
My question now is, can ln be used to work around this issue or is
that a bad idea?
It's a bad idea. Just delete the spurious DLL. No special action is
required if the cygwin dll is in the PATH.
PS. Since cgf is steadfast, perhaps
Jim Kleckner wrote:
This is helpful, thank you. Being curious and trying to be minimal
about changes
to the system in question, I tried removing and linking the dll in
place. I first tried
ln -s /bin/cygwin1.dll in the clamwin/bin directory and wasn't
surprised that it
didn't work.
At 10:20 PM 3/24/2005, you wrote:
Jim Kleckner wrote:
This is helpful, thank you. Being curious and trying to be minimal
about changes
to the system in question, I tried removing and linking the dll in
place. I first tried
ln -s /bin/cygwin1.dll in the clamwin/bin directory and wasn't
On Thu, 24 Mar 2005, Jim Kleckner wrote:
PS. Since cgf is steadfast, perhaps this explanation could be added to
the FAQ entry located here that partially explains why multiple dlls is
a problem:
http://cygwin.com/faq/faq_3.html#SEC50
We have a link for such applications:
20 matches
Mail list logo
