This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: CHERE package missing from 64-bit Setup 2.830
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 24 Oct 2013 13:36:20 -0400
- Subject: Re: CHERE package missing from 64-bit Setup 2.830
- Authentication-results: sourceware.org; auth=none
- References: <CE883C03C6B27343A6A342B05FDFA372654134 at BL2PRD0711MB433 dot namprd07 dot prod dot outlook dot com> <526840CF dot 1090803 at cygwin dot com> <CE883C03C6B27343A6A342B05FDFA372654318 at BL2PRD0711MB433 dot namprd07 dot prod dot outlook dot com>
- Reply-to: cygwin at cygwin dot com
On 10/23/2013 7:27 PM, Charles Butterfield wrote:
Larry - Thanks for your suggestions regarding mixing 32 and 64-bit
installations (CHERE, INETUTILS, PING, etc). I have a couple of follow-on
questions:
1) Can I simply copy the 32-bit binaries into the 64-bit "bin"
directory?
You could but it's not recommended. For one thing, you'd be ruining your
32-bit install and setting yourself up to overwrite the 32-bit versions
when the 64-bit ones arrive. Too messy... at least.
That is, will they work fine with the 64-bit Cygwin DLLs in the path? Or do
I need to augment my path to include the 32-bit bin directories as well
(such as in my .bashrc file)?
You can call the 32-bit from 64-bit-land (i.e. call a 32-bit "ls.exe" from
a 64-bit "bash"). If you want this to happen transparently, I'd recommend
putting the 32-bit bin path in your "PATH" environment variable after your
64-bit paths.
2) I assumed CHERE somehow encodes "where minty and bash are".
Yes, it will use the 32-bit versions of these.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple