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

2013-11-22 Thread jojelino
On 2013-11-23 AM 4:02, jojelino wrote: On 2013-11-02 PM 3:23, David Rothenberger wrote: This problem is caused by zero-byte of ${builddir}/host-i686-pc-cygwin/specs and the specs file is created by bootstrapped gcc executable. the bootstrapped gcc crashes when generating specs file, which is the

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

2013-11-22 Thread jojelino
On 2013-11-02 PM 3:23, David Rothenberger wrote: With gcc-4.8.2-1, the following fails: % touch /tmp/t.c % /bin/gcc -c /tmp/t.c gcc: error: spawn: No such file or directory This works correctly if gcc is invoked as "gcc" or "/usr/bin/gcc". It also works correctly with 4.8.1. It appears this is

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

2013-11-10 Thread Bengt Larsson
David Rothenberger wrote: >With gcc-4.8.2-1, the following fails: > >% touch /tmp/t.c >% /bin/gcc -c /tmp/t.c >gcc: error: spawn: No such file or directory > >This works correctly if gcc is invoked as "gcc" or "/usr/bin/gcc". >It also works correctly with 4.8.1. > I seem to have found something re

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

2013-11-05 Thread Corinna Vinschen
On Nov 5 11:02, Charles Wilson wrote: > 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

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

2013-11-05 Thread Charles Wilson
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 ne

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

2013-11-05 Thread Corinna Vinschen
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

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

2013-11-04 Thread Andrey Repin
Greetings, Andrey Repin! > Is this the reason for behavior such as this? > $ which -a test > /usr/bin/test > /usr/bin/test Hurr... disregard this. It appears, my problem was (is) in /etc/profile, which forces additional copy of /usr/bin to be injected into $PATH. Whoever maintain /etc/defaults/

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

2013-11-04 Thread Robert Pendell
On Mon, Nov 4, 2013 at 10:38 PM, Robert Pendell wrote: > On Mon, Nov 4, 2013 at 10:03 PM, Andrey Repin wrote: >> Greetings, Corinna Vinschen! >> >>> On Nov 2 23:54, Yaakov (Cygwin/X) wrote: On 2013-11-02 04:36, Corinna Vinschen wrote: >On Nov 1 23:23, David Rothenberger wrote: >>Wi

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

2013-11-04 Thread Robert Pendell
On Mon, Nov 4, 2013 at 10:03 PM, Andrey Repin wrote: > Greetings, Corinna Vinschen! > >> On Nov 2 23:54, Yaakov (Cygwin/X) wrote: >>> On 2013-11-02 04:36, Corinna Vinschen wrote: >>> >On Nov 1 23:23, David Rothenberger wrote: >>> >>With gcc-4.8.2-1, the following fails: >>> >> >>> >>% touch /tmp/

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

2013-11-04 Thread Andrey Repin
Greetings, Corinna Vinschen! > On Nov 2 23:54, Yaakov (Cygwin/X) wrote: >> On 2013-11-02 04:36, Corinna Vinschen wrote: >> >On Nov 1 23:23, David Rothenberger wrote: >> >>With gcc-4.8.2-1, the following fails: >> >> >> >>% touch /tmp/t.c >> >>% /bin/gcc -c /tmp/t.c >> >>gcc: error: spawn: No suc

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

2013-11-04 Thread Yaakov (Cygwin/X)
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 horrifi

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

2013-11-04 Thread Andrey Repin
Greetings, Charles Wilson! > On 11/4/2013 6:42 AM, Corinna Vinschen wrote: >> On Nov 2 23:54, Yaakov (Cygwin/X) wrote: >>> So, while I'm not convinced that this is a huge issue overall, if >>> "don't do that" isn't good enough, the easiest workaround is to >>> configure GCC with --libexecdir=/usr

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

2013-11-04 Thread Charles Wilson
On 11/4/2013 6:42 AM, Corinna Vinschen wrote: On Nov 2 23:54, Yaakov (Cygwin/X) wrote: So, while I'm not convinced that this is a huge issue overall, if "don't do that" isn't good enough, the easiest workaround is to configure GCC with --libexecdir=/usr/lib. That would be the safer option, I

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

2013-11-04 Thread Corinna Vinschen
On Nov 2 23:54, Yaakov (Cygwin/X) wrote: > On 2013-11-02 04:36, Corinna Vinschen wrote: > >On Nov 1 23:23, David Rothenberger wrote: > >>With gcc-4.8.2-1, the following fails: > >> > >>% touch /tmp/t.c > >>% /bin/gcc -c /tmp/t.c > >>gcc: error: spawn: No such file or directory > > Curious, are y

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

2013-11-03 Thread David Rothenberger
On 11/2/2013 9:54 PM, Yaakov (Cygwin/X) wrote: > On 2013-11-02 04:36, Corinna Vinschen wrote: >> On Nov 1 23:23, David Rothenberger wrote: >>> With gcc-4.8.2-1, the following fails: >>> >>> % touch /tmp/t.c >>> % /bin/gcc -c /tmp/t.c >>> gcc: error: spawn: No such file or directory > > Curious, a

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

2013-11-02 Thread Yaakov (Cygwin/X)
On 2013-11-02 04:36, Corinna Vinschen wrote: On Nov 1 23:23, David Rothenberger wrote: With gcc-4.8.2-1, the following fails: % touch /tmp/t.c % /bin/gcc -c /tmp/t.c gcc: error: spawn: No such file or directory Curious, are you seeing real-life references to /bin/gcc? Because that wouldn't

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

2013-11-02 Thread Corinna Vinschen
On Nov 1 23:23, David Rothenberger wrote: > With gcc-4.8.2-1, the following fails: > > % touch /tmp/t.c > % /bin/gcc -c /tmp/t.c > gcc: error: spawn: No such file or directory > > This works correctly if gcc is invoked as "gcc" or "/usr/bin/gcc". > It also works correctly with 4.8.1. > > It app

gcc-4.8.2-1: /bin/gcc fails

2013-11-01 Thread David Rothenberger
With gcc-4.8.2-1, the following fails: % touch /tmp/t.c % /bin/gcc -c /tmp/t.c gcc: error: spawn: No such file or directory This works correctly if gcc is invoked as "gcc" or "/usr/bin/gcc". It also works correctly with 4.8.1. It appears this is due to a change from /usr/lib to /usr/libexec. /bi