Re: gcc-4.8.2-1: /bin/gcc fails

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]

On Nov  4 20:18, Yaakov (Cygwin/X) wrote:
> On 2013-11-04 08:45, Charles Wilson wrote:
> >My about-to-be-uploaded inetutils update puts the servers in libexecdir
> >aka /usr/libexec/ -- and changes the /etc/defaults/ associated xinetd
> >and inetd.d configuration files as appropriate.  'Course, my
> >to-be-written update announcement will be a horrific, as current users
> >with customized configuration WILL have to modify their files (and setup
> >doesn't have an .rpmsave/.rpmnew mechanism).
> >
> >The currently-distributed version (and associated xinetd scripts and
> >sample inetd.d/ configuration files) puts them in /usr/sbin.
> >
> >If --libexecdir=/usr/lib, then...what?
> >
> >Should I revert to /usr/sbin for slave servers?  Use $libexecdir but
> >"know" that it is going to be /usr/lib and configure appropriately?  I'm
> >confused as to how to proceed here.
> 
> 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.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]