Openembedded Core Discussions
 help / color / mirror / Atom feed
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 14:08:13 +0300	[thread overview]
Message-ID: <20190515110813.GA13420@localhost> (raw)
In-Reply-To: <0ffc3e2e-2321-0edb-c90a-76225017472d@windriver.com>

On Wed, May 15, 2019 at 05:50:44PM +0800, Hongxu Jia wrote:
> On 5/15/19 5:32 PM, Andreas Müller wrote:
> > > --- a/meta/classes/autotools.bbclass
> > > +++ b/meta/classes/autotools.bbclass
> > > @@ -90,7 +90,11 @@ oe_runconf () {
> > >                  bbnote "Running $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} $@"
> > >                  if ! ${CACHED_CONFIGUREVARS} $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} "$@"; then
> > >                          bbnote "The following config.log files may provide further information."
> > > -                       bbnote `find ${B} -ignore_readdir_race -type f -name config.log`
> > > +                       config_log="`find ${B} -ignore_readdir_race -type f -name config.log`"
> > > +                       bbnote "$config_log"
> > > +                       [ -e "$config_log" ] && cat "$config_log" | while read line; do
> > > +                               bbnote "$line"
> > > +                       done
> > >                          bbfatal_log "configure failed"
> > >                  fi
> > >          else
> > > --
> > > 2.7.4
> > > 
> > That output is useful only sometimes and extremly verbose. I'd suggest
> > to introduce a switch to enable/disable (even as newbie user I am able
> > to find config.log). How about making autobuilder's WORKDIR
> > accessible?
> 
> The output only happens while do_configure failure, it does nothing when
> build succeed,
> 
> while failure occurs, I believe related message is the more the better.
> 
> The autobuilder is just an example, for community development, it is hard to
> login
> 
> others build host to debug issue, and we have to take time to reproduce it
> 
> if we could trace it with a simple glance from the log, why not

The end of config.log often contains expected error messages completely 
unrelated to the actual problem.

Debian autobuilders already dump config.log when when configuring failed,
and there it is a common problem that people end up searching for the 
problem in the wrong places due to that.

If possible, it would therefore be better to make it accessible separately.

> //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



  parent reply	other threads:[~2019-05-15 11:08 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 [this message]
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
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=20190515110813.GA13420@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