From: <colin.helliwell@ln-systems.com>
To: <yocto@yoctoproject.org>
Subject: Problems with 'configure' on own recipe [after moving to morty]
Date: Tue, 25 Jul 2017 15:08:48 +0100 [thread overview]
Message-ID: <097a01d3054f$89a3b940$9ceb2bc0$@ln-systems.com> (raw)
This is gonna be a bit of a hard one to describe concisely, but hoping
someone can advise me on solving it....
I have a recipe of my own for an app (NetworkManager) which fetches the
source from its git repo. This recipe works on krogoth, but is throwing up
configure errors on morty.
The recipe has a
do_configure_prepend() {
( cd ${S} ; NOCONFIGURE=yes ./autogen.sh )
}
- I seemed to need this because the git source has no ABOUT-NLS; not sure
if that's the correct fix, but 'it seemed to work' before.
The final error is
| DEBUG: Executing shell function do_configure
| ln: failed to create symbolic link '/usr/share/doc/gtk-doc.make':
Permission denied
| cp: cannot create regular file '/usr/share/doc/gtk-doc.make': Permission
denied
I'm not sure why it's trying to make the symlink in the build machine's root
(as I say, it doesn't do this on krogoth)
I'm also getting a lot of:
| NOTE: Skipping setscene dependency
virtual:native:/home/colin/100051-trunk/fsl-community-bsp/sources/poky/meta/
recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro
copying
- not sure if this is relevant/important
Freely admit I'm no autotools expert, so any suggestions welcome! Thanks
next reply other threads:[~2017-07-25 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 14:08 colin.helliwell [this message]
2017-07-25 14:20 ` Problems with 'configure' on own recipe [after moving to morty] Burton, Ross
2017-07-25 14:39 ` Colin Helliwell
2017-07-25 14:57 ` Burton, Ross
2017-07-25 15:00 ` Colin Helliwell
2017-07-25 15:25 ` Colin Helliwell
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='097a01d3054f$89a3b940$9ceb2bc0$@ln-systems.com' \
--to=colin.helliwell@ln-systems.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.