All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jon Mason" <jdmason@kudzu.us>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	poky@yoctoproject.org
Subject: Re: [poky] testimage gcc error
Date: Wed, 12 Feb 2020 15:46:11 -0500	[thread overview]
Message-ID: <CAPoiz9x-wB91mwytobFx7L_bR_M9w6jXGifab02uHJ0i--kpiQ@mail.gmail.com> (raw)
In-Reply-To: <20200211214956.GU4735@denix.org>

On Tue, Feb 11, 2020 at 4:49 PM Denys Dmytriyenko <denis@denix.org> wrote:
>
> On Tue, Feb 11, 2020 at 09:31:49PM +0000, Richard Purdie wrote:
> > On Tue, 2020-02-11 at 14:31 -0500, Jon Mason wrote:
> > > I'm seeing multiple "Command not found" errors when I run the
> > > testimage command on zeus with GCC added.  I'm sure others are
> > > testing
> > > this and not seeing an issue.  So, please let me know what I'm doing
> > > wrong.
> > >
> > > My only configuration was to add to local.conf (aside from SSTATE_DIR
> > > and DL_DIR) is:
> > > INHERIT += "testimage"
> > > IMAGE_INSTALL_append = " autoconf make gcc "
> >
> > If you put gcc-symlinks and maybe binutils-symlinks in there, does it
> > work better? Suggests we may have some gremlins in the packages used to
> > enable the tests if so...
>
> Maybe try IMAGE_INSTALL_append = " packagegroup-core-buildessential"

Adding
IMAGE_INSTALL_append = " packagegroup-core-buildessential coreutils"
corrected the problem.  "coreutils" was needed due to a missing
"install" command, which seems odd that it's not part of the
dependency tree.

However, I think there is a larger underlying problem here.  Either
the tests need to be smart enough to know when to run, or there needs
to be some dependencies for testimage to prevent this from happening.
Alternatively, better documentation somewhere on testimage and all the
tests and dependencies would save others from this problem.

Thanks,
Jon


> --
> Denys

  parent reply	other threads:[~2020-02-12 20:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 19:31 testimage gcc error Jon Mason
2020-02-11 21:31 ` [poky] " Richard Purdie
2020-02-11 21:49   ` Denys Dmytriyenko
2020-02-12  3:16     ` akuster
2020-02-12 20:47       ` Jon Mason
2020-02-12 20:46     ` Jon Mason [this message]
2020-02-12 16:18   ` Jon Mason

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=CAPoiz9x-wB91mwytobFx7L_bR_M9w6jXGifab02uHJ0i--kpiQ@mail.gmail.com \
    --to=jdmason@kudzu.us \
    --cc=denis@denix.org \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.