On Fri, Jun 09, 2017 at 03:28:40PM -0400, Tom Rini wrote: > On Fri, Jun 09, 2017 at 05:15:07PM +0100, Burton, Ross wrote: > > On 9 June 2017 at 01:00, Tom Rini <[email protected]> wrote: > > > > > In order for the dpkg perl modules to be used the must reside in the > > > versioned perl library directory (as to be in the default include path). > > > Be explicit about this location in our FILES_${PN}-perl directive, so > > > that if this breaks in the future, the recipe will fail). We can now > > > drop the custom do_configure as it wasn't fixing this problem. > > > > > > > * FILES: removed "/usr/lib/perl", added "/usr/lib/perl/None" > > > > Obviously something didn't work right! > > Oh, I see. Yes, an existing feature is that if perl isn't built yet > then no, you don't get a sane PERLVERSION. That's true today, for > example, see liburi-perl.
Oh oh, I see. Sorry, hit a per recipe staging issue. I've reproduced and figured out the fix. -- Tom -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
