meta-mono core-image-mono failing

meta-mono core-image-mono failing

[Chris Morgan]

Hello.

I'm trying to build core-image-mono for the bbb. Layers configuration:

Build Configuration:
BB_VERSION        = "1.23.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-20"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "beaglebone"
DISTRO            = "poky"
DISTRO_VERSION    = "1.6+snapshot-20140521"
TUNE_FEATURES     = "arm armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
common-bsp        =
"(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
meta-yocto
meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"

This is basically master of Poky and meta-mono.


| DEBUG: Executing shell function do_configure
| grep: configure.in: No such file or directory
| /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
line 125: mono/mini/Makefile.am: No such file or directory
| /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
line 126: mono/metadata/Makefile.am: No such file or directory
| Running aclocal -I m4 -I .  ...
| aclocal: error: 'configure.ac' is required
|
| **Error**: aclocal failed. This may mean that you have not
| installed all of the packages you need, or you may need to
| set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
| for the prefix where you installed the packages whose
| macros were not found
| NOTE: mono-native failed to autogen.sh
| sed: can't read acinclude.m4: No such file or directory
| WARNING: /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
exit 2 from
|   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
| ERROR: Function failed: do_configure (log file is located at
/home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
ERROR: Task 687
(/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
do_configure) failed with exit code '1'


It looks like the issue is due to autogen.sh assuming several files
are located in the current working directory, for instance on lines
102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
before files like configure.in or mono/metadata/Makefile.am.in etc.

Not sure if something has changed on the yocto side to change this
assumption about where autogen.sh is being run from.

Chris

Re: meta-mono core-image-mono failing

[Gary Thomas]

On 2014-05-21 12:25, Chris Morgan wrote:
> Hello.
>
> I'm trying to build core-image-mono for the bbb. Layers configuration:
>
> Build Configuration:
> BB_VERSION        = "1.23.1"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Fedora-20"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "beaglebone"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.6+snapshot-20140521"
> TUNE_FEATURES     = "arm armv7a vfp neon"
> TARGET_FPU        = "vfp-neon"
> meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
> meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
> common-bsp        =
> "(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
> meta-yocto
> meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
> meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"
>
> This is basically master of Poky and meta-mono.
>
>
> | DEBUG: Executing shell function do_configure
> | grep: configure.in: No such file or directory
> | /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
> line 125: mono/mini/Makefile.am: No such file or directory
> | /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
> line 126: mono/metadata/Makefile.am: No such file or directory
> | Running aclocal -I m4 -I .  ...
> | aclocal: error: 'configure.ac' is required
> |
> | **Error**: aclocal failed. This may mean that you have not
> | installed all of the packages you need, or you may need to
> | set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
> | for the prefix where you installed the packages whose
> | macros were not found
> | NOTE: mono-native failed to autogen.sh
> | sed: can't read acinclude.m4: No such file or directory
> | WARNING: /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
> exit 2 from
> |   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
> | ERROR: Function failed: do_configure (log file is located at
> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
> ERROR: Task 687
> (/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
> do_configure) failed with exit code '1'
>
>
> It looks like the issue is due to autogen.sh assuming several files
> are located in the current working directory, for instance on lines
> 102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
> before files like configure.in or mono/metadata/Makefile.am.in etc.
>
> Not sure if something has changed on the yocto side to change this
> assumption about where autogen.sh is being run from.

Look at your recipe(s).  The simple way to fix this is to change
'inherit autotools' to 'inherit autotools-brokensep'

You could also look at the recipe more deeply and figure out
where it assumes that ${S} == ${B} because of a recent change
in OE-core, this is no longer true when you inherit autotools.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: meta-mono core-image-mono failing

[Chris Morgan]

On Wed, May 21, 2014 at 2:57 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> On 2014-05-21 12:25, Chris Morgan wrote:
>>
>> Hello.
>>
>> I'm trying to build core-image-mono for the bbb. Layers configuration:
>>
>> Build Configuration:
>> BB_VERSION        = "1.23.1"
>> BUILD_SYS         = "x86_64-linux"
>> NATIVELSBSTRING   = "Fedora-20"
>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>> MACHINE           = "beaglebone"
>> DISTRO            = "poky"
>> DISTRO_VERSION    = "1.6+snapshot-20140521"
>> TUNE_FEATURES     = "arm armv7a vfp neon"
>> TARGET_FPU        = "vfp-neon"
>> meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>> meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
>> common-bsp        =
>> "(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
>> meta-yocto
>> meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>> meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"
>>
>> This is basically master of Poky and meta-mono.
>>
>>
>> | DEBUG: Executing shell function do_configure
>> | grep: configure.in: No such file or directory
>> |
>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>> line 125: mono/mini/Makefile.am: No such file or directory
>> |
>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>> line 126: mono/metadata/Makefile.am: No such file or directory
>> | Running aclocal -I m4 -I .  ...
>> | aclocal: error: 'configure.ac' is required
>> |
>> | **Error**: aclocal failed. This may mean that you have not
>> | installed all of the packages you need, or you may need to
>> | set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
>> | for the prefix where you installed the packages whose
>> | macros were not found
>> | NOTE: mono-native failed to autogen.sh
>> | sed: can't read acinclude.m4: No such file or directory
>> | WARNING:
>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
>> exit 2 from
>> |   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
>> | ERROR: Function failed: do_configure (log file is located at
>>
>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
>> ERROR: Task 687
>>
>> (/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
>> do_configure) failed with exit code '1'
>>
>>
>> It looks like the issue is due to autogen.sh assuming several files
>> are located in the current working directory, for instance on lines
>> 102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
>> before files like configure.in or mono/metadata/Makefile.am.in etc.
>>
>> Not sure if something has changed on the yocto side to change this
>> assumption about where autogen.sh is being run from.
>
>
> Look at your recipe(s).  The simple way to fix this is to change
> 'inherit autotools' to 'inherit autotools-brokensep'
>
> You could also look at the recipe more deeply and figure out
> where it assumes that ${S} == ${B} because of a recent change
> in OE-core, this is no longer true when you inherit autotools.
>

Testing now with autotools-brokensep in mono-3.4.0.inc.

I did look a bit and it looked like there were several places where
source and build were assumed but I'm not confident that it would be
easy to figure out what to fix and then create a patch for it but I
could look at that and feeding it back to the mono guys. Let me do
that and see how I make out.

Chris

Re: meta-mono core-image-mono failing

[Alex J Lennon]

On 21/05/2014 20:07, Chris Morgan wrote:
> On Wed, May 21, 2014 at 2:57 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2014-05-21 12:25, Chris Morgan wrote:
>>> Hello.
>>>
>>> I'm trying to build core-image-mono for the bbb. Layers configuration:
>>>
>>> Build Configuration:
>>> BB_VERSION        = "1.23.1"
>>> BUILD_SYS         = "x86_64-linux"
>>> NATIVELSBSTRING   = "Fedora-20"
>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>> MACHINE           = "beaglebone"
>>> DISTRO            = "poky"
>>> DISTRO_VERSION    = "1.6+snapshot-20140521"
>>> TUNE_FEATURES     = "arm armv7a vfp neon"
>>> TARGET_FPU        = "vfp-neon"
>>> meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>> meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
>>> common-bsp        =
>>> "(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
>>> meta-yocto
>>> meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>> meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"
>>>
>>> This is basically master of Poky and meta-mono.
>>>
>>>
>>> | DEBUG: Executing shell function do_configure
>>> | grep: configure.in: No such file or directory
>>> |
>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>> line 125: mono/mini/Makefile.am: No such file or directory
>>> |
>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>> line 126: mono/metadata/Makefile.am: No such file or directory
>>> | Running aclocal -I m4 -I .  ...
>>> | aclocal: error: 'configure.ac' is required
>>> |
>>> | **Error**: aclocal failed. This may mean that you have not
>>> | installed all of the packages you need, or you may need to
>>> | set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
>>> | for the prefix where you installed the packages whose
>>> | macros were not found
>>> | NOTE: mono-native failed to autogen.sh
>>> | sed: can't read acinclude.m4: No such file or directory
>>> | WARNING:
>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
>>> exit 2 from
>>> |   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
>>> | ERROR: Function failed: do_configure (log file is located at
>>>
>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
>>> ERROR: Task 687
>>>
>>> (/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
>>> do_configure) failed with exit code '1'
>>>
>>>
>>> It looks like the issue is due to autogen.sh assuming several files
>>> are located in the current working directory, for instance on lines
>>> 102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
>>> before files like configure.in or mono/metadata/Makefile.am.in etc.
>>>
>>> Not sure if something has changed on the yocto side to change this
>>> assumption about where autogen.sh is being run from.
>>
>> Look at your recipe(s).  The simple way to fix this is to change
>> 'inherit autotools' to 'inherit autotools-brokensep'
>>
>> You could also look at the recipe more deeply and figure out
>> where it assumes that ${S} == ${B} because of a recent change
>> in OE-core, this is no longer true when you inherit autotools.
>>
> Testing now with autotools-brokensep in mono-3.4.0.inc.
>
> I did look a bit and it looked like there were several places where
> source and build were assumed but I'm not confident that it would be
> easy to figure out what to fix and then create a patch for it but I
> could look at that and feeding it back to the mono guys. Let me do
> that and see how I make out.
>
> Chris

Strange. I've been building pretty regularly recently with daisy on
Ubuntu 12.04 without problems.

There have been issues with Linux Mint, x64 hosts, and host
installations of Mono, but I thought I had finally addressed those. It's
starting to feel a little like a game of whack-a-mole.

Can you provide me your local.conf and I'll have a look at what happens
here with your hashes for  bbb on a Fedora box.

Thanks,

Alex

Re: meta-mono core-image-mono failing

[Chris Morgan]

[-- Attachment #1: Type: text/plain, Size: 5327 bytes --]

On Wed, May 21, 2014 at 4:15 PM, Alex J Lennon
<ajlennon@dynamicdevices.co.uk> wrote:
>
> On 21/05/2014 20:07, Chris Morgan wrote:
>> On Wed, May 21, 2014 at 2:57 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>> On 2014-05-21 12:25, Chris Morgan wrote:
>>>> Hello.
>>>>
>>>> I'm trying to build core-image-mono for the bbb. Layers configuration:
>>>>
>>>> Build Configuration:
>>>> BB_VERSION        = "1.23.1"
>>>> BUILD_SYS         = "x86_64-linux"
>>>> NATIVELSBSTRING   = "Fedora-20"
>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>> MACHINE           = "beaglebone"
>>>> DISTRO            = "poky"
>>>> DISTRO_VERSION    = "1.6+snapshot-20140521"
>>>> TUNE_FEATURES     = "arm armv7a vfp neon"
>>>> TARGET_FPU        = "vfp-neon"
>>>> meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>> meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
>>>> common-bsp        =
>>>> "(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
>>>> meta-yocto
>>>> meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>> meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"
>>>>
>>>> This is basically master of Poky and meta-mono.
>>>>
>>>>
>>>> | DEBUG: Executing shell function do_configure
>>>> | grep: configure.in: No such file or directory
>>>> |
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>> line 125: mono/mini/Makefile.am: No such file or directory
>>>> |
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>> line 126: mono/metadata/Makefile.am: No such file or directory
>>>> | Running aclocal -I m4 -I .  ...
>>>> | aclocal: error: 'configure.ac' is required
>>>> |
>>>> | **Error**: aclocal failed. This may mean that you have not
>>>> | installed all of the packages you need, or you may need to
>>>> | set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
>>>> | for the prefix where you installed the packages whose
>>>> | macros were not found
>>>> | NOTE: mono-native failed to autogen.sh
>>>> | sed: can't read acinclude.m4: No such file or directory
>>>> | WARNING:
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
>>>> exit 2 from
>>>> |   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
>>>> | ERROR: Function failed: do_configure (log file is located at
>>>>
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
>>>> ERROR: Task 687
>>>>
>>>> (/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
>>>> do_configure) failed with exit code '1'
>>>>
>>>>
>>>> It looks like the issue is due to autogen.sh assuming several files
>>>> are located in the current working directory, for instance on lines
>>>> 102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
>>>> before files like configure.in or mono/metadata/Makefile.am.in etc.
>>>>
>>>> Not sure if something has changed on the yocto side to change this
>>>> assumption about where autogen.sh is being run from.
>>>
>>> Look at your recipe(s).  The simple way to fix this is to change
>>> 'inherit autotools' to 'inherit autotools-brokensep'
>>>
>>> You could also look at the recipe more deeply and figure out
>>> where it assumes that ${S} == ${B} because of a recent change
>>> in OE-core, this is no longer true when you inherit autotools.
>>>
>> Testing now with autotools-brokensep in mono-3.4.0.inc.
>>
>> I did look a bit and it looked like there were several places where
>> source and build were assumed but I'm not confident that it would be
>> easy to figure out what to fix and then create a patch for it but I
>> could look at that and feeding it back to the mono guys. Let me do
>> that and see how I make out.
>>
>> Chris
>
> Strange. I've been building pretty regularly recently with daisy on
> Ubuntu 12.04 without problems.
>
> There have been issues with Linux Mint, x64 hosts, and host
> installations of Mono, but I thought I had finally addressed those. It's
> starting to feel a little like a game of whack-a-mole.
>
> Can you provide me your local.conf and I'll have a look at what happens
> here with your hashes for  bbb on a Fedora box.
>
> Thanks,
>
> Alex
>

After this email if you still want to go down the path of getting my
configuration we can do that. I'm just using git.pokylinux.org and
meta-beaglebone from Koei with some minor changes in my local.conf to
enable systemd and force my own packages into any image that is built.

The attached patch fixes things for me here which matches what Gary
mentioned. I did not test 3.2 build, only the 3.4 one, I presume the
issue in autogen.sh is present for the older branch/version as well.

I also emailed the mono guys and Zoltan replied saying that autogen.sh
has to be run from within tree. I suspect this could be corrected by
use of $srcdir in autogen.sh but I'm not sure if I'm super
enthusiastic about going down that route if the mono guys aren't.

http://lists.ximian.com/pipermail/mono-devel-list/2014-May/041537.html

Chris

[-- Attachment #2: 0001-Switch-from-autotools-to-autotools-brokensep-to-hand.patch --]
[-- Type: text/x-patch, Size: 1431 bytes --]

From 946c3101b9801797c2c02efc5003a799d0060300 Mon Sep 17 00:00:00 2001
From: Chris Morgan <chmorgan@gmail.com>
Date: Wed, 21 May 2014 16:21:47 -0400
Subject: [PATCH] Switch from autotools to autotools-brokensep to handle Mono's
 autogen.sh requiring it be run from inside of the source tree

Signed-off-by: Chris Morgan <chmorgan@gmail.com>
---
 recipes-mono/mono/mono-3.2.8.inc | 2 +-
 recipes-mono/mono/mono-3.4.0.inc | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-mono/mono/mono-3.2.8.inc b/recipes-mono/mono/mono-3.2.8.inc
index 0fd79aa..04ea04f 100644
--- a/recipes-mono/mono/mono-3.2.8.inc
+++ b/recipes-mono/mono/mono-3.2.8.inc
@@ -7,7 +7,7 @@ LICENSE = "GPLv2"
 
 LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=80862f3fd0e11a5fa0318070c54461ce"
 
-inherit autotools 
+inherit autotools-brokensep
 
 SRC_URI = "http://download.mono-project.com/sources/mono/mono-${PV}.tar.bz2 \
 	   file://dllmap-config.in.diff \
diff --git a/recipes-mono/mono/mono-3.4.0.inc b/recipes-mono/mono/mono-3.4.0.inc
index 59b9af7..1c3dbf3 100644
--- a/recipes-mono/mono/mono-3.4.0.inc
+++ b/recipes-mono/mono/mono-3.4.0.inc
@@ -7,7 +7,7 @@ LICENSE = "GPLv2"
 
 LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=80862f3fd0e11a5fa0318070c54461ce"
 
-inherit autotools 
+inherit autotools-brokensep
 
 SRC_URI = "http://download.mono-project.com/sources/mono/mono-${PV}.tar.bz2 \
 	   file://dllmap-config.in.diff \
-- 
1.9.0

Re: meta-mono core-image-mono failing

[Alex J Lennon]

On 21/05/2014 21:26, Chris Morgan wrote:
> On Wed, May 21, 2014 at 4:15 PM, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk> wrote:
>> On 21/05/2014 20:07, Chris Morgan wrote:
>>> On Wed, May 21, 2014 at 2:57 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> On 2014-05-21 12:25, Chris Morgan wrote:
>>>>> Hello.
>>>>>
>>>>> I'm trying to build core-image-mono for the bbb. Layers configuration:
>>>>>
>>>>> Build Configuration:
>>>>> BB_VERSION        = "1.23.1"
>>>>> BUILD_SYS         = "x86_64-linux"
>>>>> NATIVELSBSTRING   = "Fedora-20"
>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>> MACHINE           = "beaglebone"
>>>>> DISTRO            = "poky"
>>>>> DISTRO_VERSION    = "1.6+snapshot-20140521"
>>>>> TUNE_FEATURES     = "arm armv7a vfp neon"
>>>>> TARGET_FPU        = "vfp-neon"
>>>>> meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>>> meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
>>>>> common-bsp        =
>>>>> "(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
>>>>> meta-yocto
>>>>> meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>>> meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"
>>>>>
>>>>> This is basically master of Poky and meta-mono.
>>>>>
>>>>>
>>>>> | DEBUG: Executing shell function do_configure
>>>>> | grep: configure.in: No such file or directory
>>>>> |
>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>>> line 125: mono/mini/Makefile.am: No such file or directory
>>>>> |
>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>>> line 126: mono/metadata/Makefile.am: No such file or directory
>>>>> | Running aclocal -I m4 -I .  ...
>>>>> | aclocal: error: 'configure.ac' is required
>>>>> |
>>>>> | **Error**: aclocal failed. This may mean that you have not
>>>>> | installed all of the packages you need, or you may need to
>>>>> | set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
>>>>> | for the prefix where you installed the packages whose
>>>>> | macros were not found
>>>>> | NOTE: mono-native failed to autogen.sh
>>>>> | sed: can't read acinclude.m4: No such file or directory
>>>>> | WARNING:
>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
>>>>> exit 2 from
>>>>> |   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
>>>>> | ERROR: Function failed: do_configure (log file is located at
>>>>>
>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
>>>>> ERROR: Task 687
>>>>>
>>>>> (/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
>>>>> do_configure) failed with exit code '1'
>>>>>
>>>>>
>>>>> It looks like the issue is due to autogen.sh assuming several files
>>>>> are located in the current working directory, for instance on lines
>>>>> 102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
>>>>> before files like configure.in or mono/metadata/Makefile.am.in etc.
>>>>>
>>>>> Not sure if something has changed on the yocto side to change this
>>>>> assumption about where autogen.sh is being run from.
>>>> Look at your recipe(s).  The simple way to fix this is to change
>>>> 'inherit autotools' to 'inherit autotools-brokensep'
>>>>
>>>> You could also look at the recipe more deeply and figure out
>>>> where it assumes that ${S} == ${B} because of a recent change
>>>> in OE-core, this is no longer true when you inherit autotools.
>>>>
>>> Testing now with autotools-brokensep in mono-3.4.0.inc.
>>>
>>> I did look a bit and it looked like there were several places where
>>> source and build were assumed but I'm not confident that it would be
>>> easy to figure out what to fix and then create a patch for it but I
>>> could look at that and feeding it back to the mono guys. Let me do
>>> that and see how I make out.
>>>
>>> Chris
>> Strange. I've been building pretty regularly recently with daisy on
>> Ubuntu 12.04 without problems.
>>
>> There have been issues with Linux Mint, x64 hosts, and host
>> installations of Mono, but I thought I had finally addressed those. It's
>> starting to feel a little like a game of whack-a-mole.
>>
>> Can you provide me your local.conf and I'll have a look at what happens
>> here with your hashes for  bbb on a Fedora box.
>>
>> Thanks,
>>
>> Alex
>>
> After this email if you still want to go down the path of getting my
> configuration we can do that. I'm just using git.pokylinux.org and
> meta-beaglebone from Koei with some minor changes in my local.conf to
> enable systemd and force my own packages into any image that is built.
>
> The attached patch fixes things for me here which matches what Gary
> mentioned. I did not test 3.2 build, only the 3.4 one, I presume the
> issue in autogen.sh is present for the older branch/version as well.

I might well be missing something here, and I wouldn't disagree with the
your comment that there could be issues with the Mono build (I
understand there's work in progress to improve it) but I'd like to
understand why this is an issue with Fedora / Beaglebone and I've not
seen the issue with Ubuntu 12.04 / { qemu, imx6, rpi, clanton }

I'll run a build of mono-native on Fedora for qemu as a smoke test, and
see what happens.

> I also emailed the mono guys and Zoltan replied saying that autogen.sh
> has to be run from within tree. I suspect this could be corrected by
> use of $srcdir in autogen.sh but I'm not sure if I'm super
> enthusiastic about going down that route if the mono guys aren't.
>
> http://lists.ximian.com/pipermail/mono-devel-list/2014-May/041537.html
>
> Chris

Re: meta-mono core-image-mono failing

[Chris Morgan]

On Wed, May 21, 2014 at 4:35 PM, Alex J Lennon
<ajlennon@dynamicdevices.co.uk> wrote:
>
> On 21/05/2014 21:26, Chris Morgan wrote:
>> On Wed, May 21, 2014 at 4:15 PM, Alex J Lennon
>> <ajlennon@dynamicdevices.co.uk> wrote:
>>> On 21/05/2014 20:07, Chris Morgan wrote:
>>>> On Wed, May 21, 2014 at 2:57 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>> On 2014-05-21 12:25, Chris Morgan wrote:
>>>>>> Hello.
>>>>>>
>>>>>> I'm trying to build core-image-mono for the bbb. Layers configuration:
>>>>>>
>>>>>> Build Configuration:
>>>>>> BB_VERSION        = "1.23.1"
>>>>>> BUILD_SYS         = "x86_64-linux"
>>>>>> NATIVELSBSTRING   = "Fedora-20"
>>>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>>>> MACHINE           = "beaglebone"
>>>>>> DISTRO            = "poky"
>>>>>> DISTRO_VERSION    = "1.6+snapshot-20140521"
>>>>>> TUNE_FEATURES     = "arm armv7a vfp neon"
>>>>>> TARGET_FPU        = "vfp-neon"
>>>>>> meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>>>> meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
>>>>>> common-bsp        =
>>>>>> "(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
>>>>>> meta-yocto
>>>>>> meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>>>> meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"
>>>>>>
>>>>>> This is basically master of Poky and meta-mono.
>>>>>>
>>>>>>
>>>>>> | DEBUG: Executing shell function do_configure
>>>>>> | grep: configure.in: No such file or directory
>>>>>> |
>>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>>>> line 125: mono/mini/Makefile.am: No such file or directory
>>>>>> |
>>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>>>> line 126: mono/metadata/Makefile.am: No such file or directory
>>>>>> | Running aclocal -I m4 -I .  ...
>>>>>> | aclocal: error: 'configure.ac' is required
>>>>>> |
>>>>>> | **Error**: aclocal failed. This may mean that you have not
>>>>>> | installed all of the packages you need, or you may need to
>>>>>> | set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
>>>>>> | for the prefix where you installed the packages whose
>>>>>> | macros were not found
>>>>>> | NOTE: mono-native failed to autogen.sh
>>>>>> | sed: can't read acinclude.m4: No such file or directory
>>>>>> | WARNING:
>>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
>>>>>> exit 2 from
>>>>>> |   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
>>>>>> | ERROR: Function failed: do_configure (log file is located at
>>>>>>
>>>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
>>>>>> ERROR: Task 687
>>>>>>
>>>>>> (/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
>>>>>> do_configure) failed with exit code '1'
>>>>>>
>>>>>>
>>>>>> It looks like the issue is due to autogen.sh assuming several files
>>>>>> are located in the current working directory, for instance on lines
>>>>>> 102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
>>>>>> before files like configure.in or mono/metadata/Makefile.am.in etc.
>>>>>>
>>>>>> Not sure if something has changed on the yocto side to change this
>>>>>> assumption about where autogen.sh is being run from.
>>>>> Look at your recipe(s).  The simple way to fix this is to change
>>>>> 'inherit autotools' to 'inherit autotools-brokensep'
>>>>>
>>>>> You could also look at the recipe more deeply and figure out
>>>>> where it assumes that ${S} == ${B} because of a recent change
>>>>> in OE-core, this is no longer true when you inherit autotools.
>>>>>
>>>> Testing now with autotools-brokensep in mono-3.4.0.inc.
>>>>
>>>> I did look a bit and it looked like there were several places where
>>>> source and build were assumed but I'm not confident that it would be
>>>> easy to figure out what to fix and then create a patch for it but I
>>>> could look at that and feeding it back to the mono guys. Let me do
>>>> that and see how I make out.
>>>>
>>>> Chris
>>> Strange. I've been building pretty regularly recently with daisy on
>>> Ubuntu 12.04 without problems.
>>>
>>> There have been issues with Linux Mint, x64 hosts, and host
>>> installations of Mono, but I thought I had finally addressed those. It's
>>> starting to feel a little like a game of whack-a-mole.
>>>
>>> Can you provide me your local.conf and I'll have a look at what happens
>>> here with your hashes for  bbb on a Fedora box.
>>>
>>> Thanks,
>>>
>>> Alex
>>>
>> After this email if you still want to go down the path of getting my
>> configuration we can do that. I'm just using git.pokylinux.org and
>> meta-beaglebone from Koei with some minor changes in my local.conf to
>> enable systemd and force my own packages into any image that is built.
>>
>> The attached patch fixes things for me here which matches what Gary
>> mentioned. I did not test 3.2 build, only the 3.4 one, I presume the
>> issue in autogen.sh is present for the older branch/version as well.
>
> I might well be missing something here, and I wouldn't disagree with the
> your comment that there could be issues with the Mono build (I
> understand there's work in progress to improve it) but I'd like to
> understand why this is an issue with Fedora / Beaglebone and I've not
> seen the issue with Ubuntu 12.04 / { qemu, imx6, rpi, clanton }
>
> I'll run a build of mono-native on Fedora for qemu as a smoke test, and
> see what happens.
>
>> I also emailed the mono guys and Zoltan replied saying that autogen.sh
>> has to be run from within tree. I suspect this could be corrected by
>> use of $srcdir in autogen.sh but I'm not sure if I'm super
>> enthusiastic about going down that route if the mono guys aren't.
>>
>> http://lists.ximian.com/pipermail/mono-devel-list/2014-May/041537.html
>>
>> Chris
>
>

Alright, simpler steps to reproduce, no meta-beaglebone involved or
any local.conf file changes, just the bblayers.conf addition of
meta-mono:


git clone git://git.pokylinux.org/poky.git poky_mono_test
cd poky_mono_test
git clone git://git.yoctoproject.org/meta-mono
. oe-init-build-env build
nano conf/bblayers.conf (add meta-mono)
bitbake core-image-mono


| DEBUG: Executing shell function do_configure
| grep: configure.in: No such file or directory
| /home/cmorgan/projects/poky_mono_test/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
line 125: mono/mini/Makefile.am: No such file or directory
| /home/cmorgan/projects/poky_mono_test/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
line 126: mono/metadata/Makefile.am: No such file or directory
| Running aclocal -I m4 -I .  ...
| aclocal: error: 'configure.ac' is required
|
| **Error**: aclocal failed. This may mean that you have not
| installed all of the packages you need, or you may need to
| set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
| for the prefix where you installed the packages whose
| macros were not found
| NOTE: mono-native failed to autogen.sh
| sed: can't read acinclude.m4: No such file or directory
| WARNING: /home/cmorgan/projects/poky_mono_test/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.19060:1
exit 2 from
|   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
| ERROR: Function failed: do_configure (log file is located at
/home/cmorgan/projects/poky_mono_test/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.19060)
ERROR: Task 826
(/home/cmorgan/projects/poky_mono_test/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
do_configure) failed with exit code '1'
Currently 2 running tasks (2646 of 4965):


Chris

Re: meta-mono core-image-mono failing

[Alex J Lennon]

> After this email if you still want to go down the path of getting my
> configuration we can do that. I'm just using git.pokylinux.org and
> meta-beaglebone from Koei with some minor changes in my local.conf to
> enable systemd and force my own packages into any image that is built.
>
> The attached patch fixes things for me here which matches what Gary
> mentioned. I did not test 3.2 build, only the 3.4 one, I presume the
> issue in autogen.sh is present for the older branch/version as well.
>
> I also emailed the mono guys and Zoltan replied saying that autogen.sh
> has to be run from within tree. I suspect this could be corrected by
> use of $srcdir in autogen.sh but I'm not sure if I'm super
> enthusiastic about going down that route if the mono guys aren't.
>
> http://lists.ximian.com/pipermail/mono-devel-list/2014-May/041537.html
>
> Chris

Given Miguel's latest response
(http://lists.ximian.com/pipermail/mono-devel-list/2014-May/041542.html)
I've applied your patch to master until such time as somebody is in a
positon to look at out of tree support for the mono build.

Cheers, Alex

Re: meta-mono core-image-mono failing

[Stefan Stanacar]

On Wed, May 21, 2014 at 11:15 PM, Alex J Lennon
<ajlennon@dynamicdevices.co.uk> wrote:
>
> On 21/05/2014 20:07, Chris Morgan wrote:
>> On Wed, May 21, 2014 at 2:57 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>> On 2014-05-21 12:25, Chris Morgan wrote:
>>>> Hello.
>>>>
>>>> I'm trying to build core-image-mono for the bbb. Layers configuration:
>>>>
>>>> Build Configuration:
>>>> BB_VERSION        = "1.23.1"
>>>> BUILD_SYS         = "x86_64-linux"
>>>> NATIVELSBSTRING   = "Fedora-20"
>>>> TARGET_SYS        = "arm-poky-linux-gnueabi"
>>>> MACHINE           = "beaglebone"
>>>> DISTRO            = "poky"
>>>> DISTRO_VERSION    = "1.6+snapshot-20140521"
>>>> TUNE_FEATURES     = "arm armv7a vfp neon"
>>>> TARGET_FPU        = "vfp-neon"
>>>> meta              = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>> meta-bbb          = "master:8318556523a747b7e9c97326bef14922a154e8a2"
>>>> common-bsp        =
>>>> "(detachedfrome7dc54e):e7dc54e66f4b5c2982a30bef5c67d734e9c759f5"
>>>> meta-yocto
>>>> meta-yocto-bsp    = "master:8293f564685d0f587ab63a107285625dc4f98f1c"
>>>> meta-mono         = "master:e2d2b8a518403a255822022c9e15f116c91b5dd1"
>>>>
>>>> This is basically master of Poky and meta-mono.
>>>>
>>>>
>>>> | DEBUG: Executing shell function do_configure
>>>> | grep: configure.in: No such file or directory
>>>> |
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>> line 125: mono/mini/Makefile.am: No such file or directory
>>>> |
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/mono-3.4.0/autogen.sh:
>>>> line 126: mono/metadata/Makefile.am: No such file or directory
>>>> | Running aclocal -I m4 -I .  ...
>>>> | aclocal: error: 'configure.ac' is required
>>>> |
>>>> | **Error**: aclocal failed. This may mean that you have not
>>>> | installed all of the packages you need, or you may need to
>>>> | set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
>>>> | for the prefix where you installed the packages whose
>>>> | macros were not found
>>>> | NOTE: mono-native failed to autogen.sh
>>>> | sed: can't read acinclude.m4: No such file or directory
>>>> | WARNING:
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/run.do_configure.24402:1
>>>> exit 2 from
>>>> |   sed -e "s|slash\}libtool|slash\}x86_64-linux-libtool|" -i acinclude.m4
>>>> | ERROR: Function failed: do_configure (log file is located at
>>>>
>>>> /home/cmorgan/projects/yocto_poky/build/tmp/work/x86_64-linux/mono-native/3.4.0-r0/temp/log.do_configure.24402)
>>>> ERROR: Task 687
>>>>
>>>> (/home/cmorgan/projects/yocto_poky/meta-mono/recipes-mono/mono/mono-native_3.4.0.bb,
>>>> do_configure) failed with exit code '1'
>>>>
>>>>
>>>> It looks like the issue is due to autogen.sh assuming several files
>>>> are located in the current working directory, for instance on lines
>>>> 102, 129 and 130 of autogen.sh there is no use of the $srcdir variable
>>>> before files like configure.in or mono/metadata/Makefile.am.in etc.
>>>>
>>>> Not sure if something has changed on the yocto side to change this
>>>> assumption about where autogen.sh is being run from.
>>>
>>> Look at your recipe(s).  The simple way to fix this is to change
>>> 'inherit autotools' to 'inherit autotools-brokensep'
>>>
>>> You could also look at the recipe more deeply and figure out
>>> where it assumes that ${S} == ${B} because of a recent change
>>> in OE-core, this is no longer true when you inherit autotools.
>>>
>> Testing now with autotools-brokensep in mono-3.4.0.inc.
>>
>> I did look a bit and it looked like there were several places where
>> source and build were assumed but I'm not confident that it would be
>> easy to figure out what to fix and then create a patch for it but I
>> could look at that and feeding it back to the mono guys. Let me do
>> that and see how I make out.
>>
>> Chris
>
> Strange. I've been building pretty regularly recently with daisy on
> Ubuntu 12.04 without problems.
>
> There have been issues with Linux Mint, x64 hosts, and host
> installations of Mono, but I thought I had finally addressed those. It's
> starting to feel a little like a game of whack-a-mole.
>
> Can you provide me your local.conf and I'll have a look at what happens
> here with your hashes for  bbb on a Fedora box.
>


The reason you don't see this is because you are building on daisy,
but Chris is building on master. I doubt it it has something to do
with the host distro.
Specifically master enables separate build dir by default in
autotools.bbclass whereas daisy doesn't.

Daisy has these:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=daisy&id=bf33e93f162c9fbba079b4de01c35dcb367c0577
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=daisy&id=069de520ec864fc78084e8f1ddfb20edaab55f5e

which enable only the core recipes and then marks the broken ones, but
master has one more:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=69b6eaca3d9b635e8a61a0fdbd814b558e91901d


which breaks other layers with recipes that don't work with B!=S and
they should either get fixed or use autotools-brokensep, so I guess
Chris's patch is the way to go for now...

Cheers,
Stefan


> Thanks,
>
> Alex
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: meta-mono core-image-mono failing

[Alex J Lennon]

>
> The reason you don't see this is because you are building on daisy,
> but Chris is building on master. I doubt it it has something to do
> with the host distro.
> Specifically master enables separate build dir by default in
> autotools.bbclass whereas daisy doesn't.
>
> Daisy has these:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=daisy&id=bf33e93f162c9fbba079b4de01c35dcb367c0577
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=daisy&id=069de520ec864fc78084e8f1ddfb20edaab55f5e
>
> which enable only the core recipes and then marks the broken ones, but
> master has one more:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=69b6eaca3d9b635e8a61a0fdbd814b558e91901d
>
>
> which breaks other layers with recipes that don't work with B!=S and
> they should either get fixed or use autotools-brokensep, so I guess
> Chris's patch is the way to go for now...
>
> Cheers,
> Stefan
>

Thanks Stefan.  > daisy was my suspicion but that seemed unlikely so I
have a clean Fedora build underway with daisy / meta-mono /
core-image-mono to prove it to myself as a first pass before trying master.

As I do this I am thinking it would be nice if there were canonical
images of Yocto-X.Y available to run up on Amazon/Azure/elsewhere to
prove these things out in the background without mashing my SSDs.

I am guessing somebody has done this already but I hunted around Amazon
and couldn't see any community images that looked useful (?)

Similarly (and I confess I haven't yet had time to understand
AutoBuilder as I should) presumably there are a number of daily builds
in the cloud, on each of the supported host platforms, for each of the
advertised layers, and if they fail then maintainers are kicked? Is that
how things work? If so, can you advise how I request to add meta-mono to
the kick-list?

Cheers,

Alex
 

Re: meta-mono core-image-mono failing

[Richard Purdie]

On Thu, 2014-05-22 at 00:23 +0100, Alex J Lennon wrote:
> Thanks Stefan.  > daisy was my suspicion but that seemed unlikely so I
> have a clean Fedora build underway with daisy / meta-mono /
> core-image-mono to prove it to myself as a first pass before trying master.
> 
> As I do this I am thinking it would be nice if there were canonical
> images of Yocto-X.Y available to run up on Amazon/Azure/elsewhere to
> prove these things out in the background without mashing my SSDs.
> 
> I am guessing somebody has done this already but I hunted around Amazon
> and couldn't see any community images that looked useful (?)
> 
> Similarly (and I confess I haven't yet had time to understand
> AutoBuilder as I should) presumably there are a number of daily builds
> in the cloud, on each of the supported host platforms, for each of the
> advertised layers, and if they fail then maintainers are kicked? Is that
> how things work? If so, can you advise how I request to add meta-mono to
> the kick-list?

Its a nice idea but right now we struggle to test and keep OE-Core
building, let alone trying to define tests for every other layer :(. The
amount of time I and others spend on this for OE-Core is phenomenal.

If we had more people and resources, sure but right now there is no such
setup.

Cheers,

Richard

Re: meta-mono core-image-mono failing

[Alex J Lennon]

On 22/05/2014 09:23, Richard Purdie wrote:
> On Thu, 2014-05-22 at 00:23 +0100, Alex J Lennon wrote:
>> Thanks Stefan.  > daisy was my suspicion but that seemed unlikely so I
>> have a clean Fedora build underway with daisy / meta-mono /
>> core-image-mono to prove it to myself as a first pass before trying master.
>>
>> As I do this I am thinking it would be nice if there were canonical
>> images of Yocto-X.Y available to run up on Amazon/Azure/elsewhere to
>> prove these things out in the background without mashing my SSDs.
>>
>> I am guessing somebody has done this already but I hunted around Amazon
>> and couldn't see any community images that looked useful (?)
>>
>> Similarly (and I confess I haven't yet had time to understand
>> AutoBuilder as I should) presumably there are a number of daily builds
>> in the cloud, on each of the supported host platforms, for each of the
>> advertised layers, and if they fail then maintainers are kicked? Is that
>> how things work? If so, can you advise how I request to add meta-mono to
>> the kick-list?
> Its a nice idea but right now we struggle to test and keep OE-Core
> building, let alone trying to define tests for every other layer :(. The
> amount of time I and others spend on this for OE-Core is phenomenal.

I can well imagine Richard! I've often wondered how the team(s) manage
to keep everything running along so smoothly.

>
> If we had more people and resources, sure but right now there is no such
> setup.

Like you I'm very time constrained here unfortunately, but I like the
idea of having some baseline VM images ready to go on Amazon or Azure as
a starting point for testing at least.

If such a thing hasn't already been done I might try to put those
together. If I do get around to it I'll you know (if of interest)

Cheers,

Alex

Re: meta-mono core-image-mono failing

[Richard Purdie]

On Thu, 2014-05-22 at 09:29 +0100, Alex J Lennon wrote:
> On 22/05/2014 09:23, Richard Purdie wrote:
> > On Thu, 2014-05-22 at 00:23 +0100, Alex J Lennon wrote:
> >> Thanks Stefan.  > daisy was my suspicion but that seemed unlikely so I
> >> have a clean Fedora build underway with daisy / meta-mono /
> >> core-image-mono to prove it to myself as a first pass before trying master.
> >>
> >> As I do this I am thinking it would be nice if there were canonical
> >> images of Yocto-X.Y available to run up on Amazon/Azure/elsewhere to
> >> prove these things out in the background without mashing my SSDs.
> >>
> >> I am guessing somebody has done this already but I hunted around Amazon
> >> and couldn't see any community images that looked useful (?)
> >>
> >> Similarly (and I confess I haven't yet had time to understand
> >> AutoBuilder as I should) presumably there are a number of daily builds
> >> in the cloud, on each of the supported host platforms, for each of the
> >> advertised layers, and if they fail then maintainers are kicked? Is that
> >> how things work? If so, can you advise how I request to add meta-mono to
> >> the kick-list?
> > Its a nice idea but right now we struggle to test and keep OE-Core
> > building, let alone trying to define tests for every other layer :(. The
> > amount of time I and others spend on this for OE-Core is phenomenal.
> 
> I can well imagine Richard! I've often wondered how the team(s) manage
> to keep everything running along so smoothly.
> 
> >
> > If we had more people and resources, sure but right now there is no such
> > setup.
> 
> Like you I'm very time constrained here unfortunately, but I like the
> idea of having some baseline VM images ready to go on Amazon or Azure as
> a starting point for testing at least.
> 
> If such a thing hasn't already been done I might try to put those
> together. If I do get around to it I'll you know (if of interest)

FWIW we do have the build-appliance image and that is able to run builds
within it. It sounds like you just need a slightly different version of
that (with the UI removed).

Cheers,

Richard

Re: meta-mono core-image-mono failing

[Alex J Lennon]

On 22/05/2014 09:40, Richard Purdie wrote:
> On Thu, 2014-05-22 at 09:29 +0100, Alex J Lennon wrote:
>> On 22/05/2014 09:23, Richard Purdie wrote:
>>> On Thu, 2014-05-22 at 00:23 +0100, Alex J Lennon wrote:
>>>> Thanks Stefan.  > daisy was my suspicion but that seemed unlikely so I
>>>> have a clean Fedora build underway with daisy / meta-mono /
>>>> core-image-mono to prove it to myself as a first pass before trying master.
>>>>
>>>> As I do this I am thinking it would be nice if there were canonical
>>>> images of Yocto-X.Y available to run up on Amazon/Azure/elsewhere to
>>>> prove these things out in the background without mashing my SSDs.
>>>>
>>>> I am guessing somebody has done this already but I hunted around Amazon
>>>> and couldn't see any community images that looked useful (?)
>>>>
>>>> Similarly (and I confess I haven't yet had time to understand
>>>> AutoBuilder as I should) presumably there are a number of daily builds
>>>> in the cloud, on each of the supported host platforms, for each of the
>>>> advertised layers, and if they fail then maintainers are kicked? Is that
>>>> how things work? If so, can you advise how I request to add meta-mono to
>>>> the kick-list?
>>> Its a nice idea but right now we struggle to test and keep OE-Core
>>> building, let alone trying to define tests for every other layer :(. The
>>> amount of time I and others spend on this for OE-Core is phenomenal.
>> I can well imagine Richard! I've often wondered how the team(s) manage
>> to keep everything running along so smoothly.
>>
>>> If we had more people and resources, sure but right now there is no such
>>> setup.
>> Like you I'm very time constrained here unfortunately, but I like the
>> idea of having some baseline VM images ready to go on Amazon or Azure as
>> a starting point for testing at least.
>>
>> If such a thing hasn't already been done I might try to put those
>> together. If I do get around to it I'll you know (if of interest)
> FWIW we do have the build-appliance image and that is able to run builds
> within it. It sounds like you just need a slightly different version of
> that (with the UI removed).

Thanks Richard. That sounds useful.

So, I have the build-appliance image running in VMWare. I was also
looking at the design document here,

https://wiki.yoctoproject.org/wiki/Build_Appliance_Design

The appliance image seems quite large, at 4GB for the vmdk or so
uncompressed, in the context of aiming for a 100MB download?

Looking at the f/s it seems most of this is because the sources have
already been downloaded and the native recipes built?

3.5G    ./build/downloads
1.3G    ./build/tmp/work
2.1G    ./build/tmp
5.5G    ./build
5.6G    .

I guess there's a tradeoff here between getting started building images
within the appliance quickly and the size of the appliance download?

Then, looking at the running virtual machine, it seems that if I do
something like bitbake build-appliance on my own Ubuntu 12.04 host I
would generate an appliance targetted at qemux86-64?

What I'd believe I'd like to have is ready-to-run images of the vanilla
host installations ( Fedora, OpenSUSE, Debian, and Ubuntu, x32 x64),
prepped with needed Yocto dependencies and a baseline daisy tree, to
verify Yocto build in those host environments.

I don't quite understand what elements of "my" build host actually get
pulled into the appliance image that is built (I suspect none?)

So I wonder if there's a way with the appliance to build something that
I can then sit on top of those vanilla host installations (possibly with
a separate block store image somewhere in AWS containing all the
downloads so I don't have that replicated across the images).

Does that make sense? Can you offer any advice on how to achieve that?

Thanks,

Alex