From: Adrian Bunk <bunk@stusta.de>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] autotools.bbclass: output failed config.log
Date: Wed, 15 May 2019 17:02:53 +0300 [thread overview]
Message-ID: <20190515140253.GA23229@localhost> (raw)
In-Reply-To: <da1db475-e2ea-d474-e335-1c56285b9361@windriver.com>
On Wed, May 15, 2019 at 09:50:35PM +0800, Hongxu Jia wrote:
>
> After applying my fix, here is the sample
>
> ...
>
> checking for i586-wrs-linux-gcc... i586-wrs-linux-gcc -m32 -march=i586 --sysroot=/buildarea1/hjia/wrlinux-1019/build_master-wr_qemux86_2019051509/build/tmp-glibc/work/i586-wrs-linux/grub/2.02-r0/recipe-sysroot
> checking whether the C compiler works... no
> configure: error: in `/buildarea1/hjia/wrlinux-1019/build_master-wr_qemux86_2019051509/build/tmp-glibc/work/i586-wrs-linux/grub/2.02-r0/build':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> NOTE: The following config.log files may provide further information.
> NOTE: /buildarea1/hjia/wrlinux-1019/build_master-wr_qemux86_2019051509/build/tmp-glibc/work/i586-wrs-linux/grub/2.02-r0/build/config.log
> NOTE: This file contains any messages produced by compilers while
> NOTE: running configure, to aid debugging if configure makes a mistake.
>
> ...
>
> The content of config.log has prefix `NOTE:' and also tells user
>...
The problem is that the last > 1000 lines are NOTE: - and they all get
dumped to the terminal.
It is a problem when you have to scroll up through more than a thousand
lines of mostly irrelvant information before you are seeing the most
relevant information.
> //Hongxu
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-05-15 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 9:23 [PATCH] autotools.bbclass: output failed config.log Hongxu Jia
2019-05-15 9:32 ` Andreas Müller
2019-05-15 9:50 ` Hongxu Jia
2019-05-15 10:54 ` Andreas Müller
2019-05-15 11:57 ` Hongxu Jia
2019-05-15 11:08 ` Adrian Bunk
2019-05-15 12:30 ` Hongxu Jia
2019-05-15 13:42 ` Adrian Bunk
2019-05-15 13:50 ` Hongxu Jia
2019-05-15 13:53 ` Hongxu Jia
2019-05-15 14:02 ` Adrian Bunk [this message]
2019-05-20 20:50 ` Khem Raj
2019-05-15 13:32 ` [PATCH V2] " Hongxu Jia
2019-05-15 14:01 ` richard.purdie
2019-05-15 14:05 ` Hongxu Jia
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=20190515140253.GA23229@localhost \
--to=bunk@stusta.de \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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