This is the mail archive of the
mailing list for the Cygwin project.
Re: gcc-4.8.2-1: /bin/gcc fails
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 05 Nov 2013 11:02:16 -0500
- Subject: Re: gcc-4.8.2-1: /bin/gcc fails
- Authentication-results: sourceware.org; auth=none
- References: <52749A63 dot 70803 at acm dot org> <20131102093635 dot GB25012 at calimero dot vinschen dot de> <5275D706 dot 5030207 at users dot sourceforge dot net> <20131104114204 dot GB2731 at calimero dot vinschen dot de> <5277B2F3 dot 1060705 at cwilson dot fastmail dot fm> <5278557C dot 2090205 at users dot sourceforge dot net> <20131105095221 dot GA29697 at calimero dot vinschen dot de>
On 11/5/2013 4:52 AM, Corinna Vinschen wrote:
On Nov 4 20:18, Yaakov (Cygwin/X) wrote:
Under the circumstances, configuring inetutils with
--libexecdir=/usr/sbin makes the most sense.
Full ACK. Otherwise you'd have to provide some script which tweaks an
existing /etc/inetd.conf to use the new paths. Possible, but hardly
worth the effort.
That's fine for me, but the other servers, maintained by others ,
which may or may not by started by inetd/xinetd would also need to
configure as --libexecdir=/usr/sbin, or THEY would need to tweak
This seems...counter-intuitive. "cygwin follows the LSB and <the stuff>
goes in /usr/libexec, except when it's too hard so there is the
following list of exceptions...." Is that the policy going forward?
I wasn't planning to auto-update config scripts. I was going to update
the /etc/default/* scripts , and then WARN IN BIG LETTERS in the
announcement that folks will need to manually merge the changes if
they've modified their configuration files. I know nobody will read it,
but when the inevitable queries reach the mailing list I'll be able to
point to the ANNOUNCE post.
 rsh-server, tftp-server, etc.
 this is WHY we have an /etc/default/ area after all -- to provide
updates when configurations OUGHT to change, but without clobbering a
user's customizations. The downside, even on GNU/Linux, is that the
user must manually merge. Fedora provides tools to help do this, but it
is still a manual process.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple