Re: installation location of packages
Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to [EMAIL PROTECTED] on 1/22/2006 2:13 PM: It seems to me that the cygwin packages are installed in different locations than the locations they would go if ./compile make make install are performed on the source. Yes, many packages default to an installation prefix of /usr/local if no options were given to ./configure, while cygwin packages intentionally override this with ./configure --prefix=/usr. This distinction is recommended by the FHS (http://www.pathname.com/fhs/) so that you can compile local updates of your favorite programs to /usr/local/bin without overwriting the shipped system programs in /usr/bin. But if you use setup.exe to grab the sources, every one of those src tarballs should come with directions (and usually with a script) that tells you exactly which options were passed to ./configure when building the official cygwin release of that package. Thanks a lot for the clarification! Iv. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: installation location of packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to [EMAIL PROTECTED] on 1/22/2006 2:13 PM: > It seems to me that the cygwin packages are installed in different > locations than the locations they would go if ./compile make make > install are performed on the source. Yes, many packages default to an installation prefix of /usr/local if no options were given to ./configure, while cygwin packages intentionally override this with ./configure --prefix=/usr. This distinction is recommended by the FHS (http://www.pathname.com/fhs/) so that you can compile local updates of your favorite programs to /usr/local/bin without overwriting the shipped system programs in /usr/bin. But if you use setup.exe to grab the sources, every one of those src tarballs should come with directions (and usually with a script) that tells you exactly which options were passed to ./configure when building the official cygwin release of that package. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD1NxB84KuGfSFAYARAv0kAKCJ8C8zwl+S+xyM9bSbe5hyEp1a8QCdF/Fv kpIKbB/Wx1SL5aNnlg+EHbQ= =tytV -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: installation location of packages
pobox wrote: It seems to me that the cygwin packages are installed in different locations than the locations they would go if ./compile make make install are performed on the source. Is that true No, not generally. Of course, if you're having a specific issue and want to post the details, then perhaps someone on the list can make a more specific comment or suggestion. and if yes are there anywhere instructions where these locations are so that they can be pointed to applications depending on them, when such applications are compiled. At the moment I am trying to compile Cyrus IMAP and as it seems I have to compile from source a lot of stuff it requires because things do not seem to find the cygwin packages, though these packages are installed. Did you run configure? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
installation location of packages
It seems to me that the cygwin packages are installed in different locations than the locations they would go if ./compile make make install are performed on the source. Is that true and if yes are there anywhere instructions where these locations are so that they can be pointed to applications depending on them, when such applications are compiled. At the moment I am trying to compile Cyrus IMAP and as it seems I have to compile from source a lot of stuff it requires because things do not seem to find the cygwin packages, though these packages are installed. Thanks, Iv -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
