From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot autobuilder: make[2]: c: Command not found
Date: Wed, 5 Dec 2018 09:06:28 +0100 [thread overview]
Message-ID: <20181205080628.GE11195@scaer> (raw)
In-Reply-To: <225065e1ea283f69952dae60f05daca8e93ebc27.camel@synopsys.com>
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-12-05 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 7:29 [Buildroot] Buildroot autobuilder: make[2]: c: Command not found Alexey Brodkin
2018-12-05 8:06 ` Yann E. MORIN [this message]
2018-12-05 10:35 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181205080628.GE11195@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox