From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>, yocto@yoctoproject.org
Subject: Re: sysroot question
Date: Wed, 08 Feb 2017 13:57:41 +0000 [thread overview]
Message-ID: <1486562261.3754.6.camel@linux.intel.com> (raw)
In-Reply-To: <89ae4442-5ec2-7d25-1245-dc4e9af683b9@mlbassoc.com>
On Wed, 2017-02-08 at 12:12 +0100, Gary Thomas wrote:
> On 2017-02-08 11:42, Gary Thomas wrote:
> > I had a recipe that used to work and now fails after the change
> > to the split sysroots. I'm building an out-of-tree kernel module
> > and patterned my recipe after the meta-skeleton example. My recipe
> > has this setup:
> >
> > inherit module-base kernel-module-split
> >
> > do_compile() {
> > unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS
> > oe_runmake KERNEL_PATH=${STAGING_KERNEL_DIR} \
> > KERNEL_VERSION=${KERNEL_VERSION} \
> > CC="${KERNEL_CC}" LD="${KERNEL_LD}" \
> > AR="${KERNEL_AR}" \
> > O=${STAGING_KERNEL_BUILDDIR} \
> > install
> > }
> >
> > The problem is that ${CC} (arm-amltd-linux-gnueabi-gcc) can no
> > longer be
> > found. I know it's available, just not sure what needs to change
> > to be
> > able to find it.
> >
> > $ find tmp/work/teton_p7618-amltd-linux-gnueabi/my-module/ -name
> > "arm*gcc"
> > tmp/work/teton_p7618-amltd-linux-gnueabi/my-module/5.2.2-r2-
> > r0/recipe-sysroot-native/usr/libexec/arm-amltd-linux-
> > gnueabi/gcc/arm-amltd-linux-gnueabi/5.4.0/arm-amltd-linux-gnueabi-
> > gcc
> >
> > tmp/work/teton_p7618-amltd-linux-gnueabi/my-module/5.2.2-r2-
> > r0/recipe-sysroot-native/usr/bin/arm-amltd-linux-gnueabi/arm-amltd-
> > linux-gnueabi-gcc
> >
> >
> >
> > Any suggestions on how I fix this?
> >
> > Thanks
> >
>
> It looks like the failure is actually happening in a class method
> (make_scripts)
> My recipe also contains this
> addtask make_scripts after do_patch before do_compile
> which doesn't seem to be setting the ${PATH} correctly anymore.
>
> Any ideas what might be missing?
Does make_scripts set cwd using the dirs varflag?
http://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-use
r-manual.html#variable-flags
i.e. meta/classes/base.bbclass:do_compile[dirs] = "${B}"
Joshua
next prev parent reply other threads:[~2017-02-08 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 10:42 sysroot question Gary Thomas
2017-02-08 11:12 ` Gary Thomas
2017-02-08 13:57 ` Joshua Lock [this message]
2017-02-08 19:36 ` Paul Eggleton
2017-02-09 4:23 ` Gary Thomas
2017-02-09 7:49 ` Anders Darander
2017-02-09 8:04 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2011-01-17 19:46 Zhang, Jessica
2011-01-17 20:01 ` Mark Hatle
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=1486562261.3754.6.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.