This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: gcc-4.8.2-1: /bin/gcc fails
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin at cygwin dot com
- Date: Mon, 04 Nov 2013 20:18:36 -0600
- 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>
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.
Yaakov
--
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