From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yann E. MORIN Date: Wed, 5 Dec 2018 09:06:28 +0100 Subject: [Buildroot] Buildroot autobuilder: make[2]: c: Command not found In-Reply-To: <225065e1ea283f69952dae60f05daca8e93ebc27.camel@synopsys.com> References: <225065e1ea283f69952dae60f05daca8e93ebc27.camel@synopsys.com> Message-ID: <20181205080628.GE11195@scaer> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Alexey, All, On 2018-12-05 07:29 +0000, Alexey Brodkin spake thusly: > Just got a report about failed build, see > http://autobuild.buildroot.net/results/cb5/cb555a124bb3bdb9c5a3465673c21022d94cf2ca/ > > But there's definitely something strange there as instead of "gcc" command "c" gets executed, > see http://autobuild.buildroot.net/results/cb5/cb555a124bb3bdb9c5a3465673c21022d94cf2ca//build-end.log: > ------------------------>8----------------------- > c -o option.o -pipe -ffunction-sections -O2 -g -I/home/buildroot/autobuild/run/instance-0/output/build/qt5base-5.6.3/qmake [--SNIP--] > make[2]: c: Command not found It furiously looks like a variable was expanded to an empty string, and thus a command in the form of: $(CC) -c -o blabla got turned into this: -c -o blabla which make interprets as running the 'c' command with blabla params, but the leading dash instructs it to ignore any failure. I've spun a build here to investigate. If I can't reproduce lcoally, I'll see to try and reproduce it on my autobuild instance. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'