Problems with 'configure' on own recipe [after moving to morty]
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
Quoted 6 lines · On 25 July 2017 at 15:08, <[email protected]> wrote:
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.
For a start, why not use the recipe from meta-oe?
Quoted 7 lines
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.
If the only thing that is missing is an ABOUT-NLS file (sounds like something gettext should have installed?) then I'd just have a prepend that touches that file, and let autotools.bbclass invoke autoreconf for you.
Quoted 11 lines
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
That's just verbose logging from the recipe-specific-sysroot code, you can ignore it.
Ross
Quoted 13 lines · Ross
Quoted 5 lines · On 25 July 2017 at 15:08, <[email protected]> wrote:
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.For a start, why not use the recipe from meta-oe?
That is in fact what I blagged as the starting point for 'my' recipe, but then evolved it so as to use the github head. For my particular [embedded] platform I also need to switch off some of the configure options.
Quoted 8 lines
Quoted 6 lines
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.If the only thing that is missing is an ABOUT-NLS file (sounds like something gettext should have installed?) then I'd just have a prepend that touches that file, and let autotools.bbclass invoke autoreconf for you.
I'll try that
Quoted 7 lines
Quoted 7 lines
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
Quoted 6 lines
Quoted 3 lines
- not sure if this is relevant/important
Freely admit I'm no autotools expert, so any suggestions welcome! Thanks
That's just verbose logging from the recipe-specific-sysroot code, you can ignore it.
Ok, ta
Quoted 3 lines · Colin Helliwell
That is in fact what I blagged as the starting point for 'my' recipe, but then evolved it so as to use the github head. For my particular [embedded] platform I also need to switch off some of the configure options.
Sounds like a bbappend should be able to fiddle SRC_URI and some PACKAGECONFIGs right?
Ross
Ah yes, that's true Ross - I should be able to try that approach instead.
Quoted 9 lines · Ross
Quoted 1 line · Colin Helliwell
That is in fact what I blagged as the starting point for 'my' recipe, but then evolved it so as to use the github head. For my particular [embedded] platform I also need to switch off some of the configure options.
Sounds like a bbappend should be able to fiddle
SRC_URIand some PACKAGECONFIGs right?Ross
Quoted 5 lines · On 25 July 2017 at 16:00 Colin Helliwell <[email protected]> wrote:
Ah yes, that's true Ross - I should be able to try that approach instead.
However.... there's obviously been a lot of changes from 1.4 to 1.8 and hence something to be said for a fresh recipe rather than mega-appending an older one..? (Well, there certainly would be if it worked....!) And, as I say, the recipe works on krogoth [cleanly rebuilt today and definitely the same git version] - something subtly changed in some or other class perhaps, but not obvious to me.
Quoted 8 lines
Quoted 8 lines · Ross
Quoted 1 line · Colin Helliwell
That is in fact what I blagged as the starting point for 'my' recipe, but then evolved it so as to use the github head. For my particular [embedded] platform I also need to switch off some of the configure options.
Sounds like a bbappend should be able to fiddle
SRC_URIand some PACKAGECONFIGs right?