gcc-4.8.2-1: /bin/gcc fails
Charles Wilson
cygwin@cwilson.fastmail.fm
Tue Nov 5 16:03:00 GMT 2013
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 [1],
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
configurations.
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 [2], 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.
[1] rsh-server, tftp-server, etc.
[2] 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.
--
Chuck
--
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
More information about the Cygwin
mailing list