[yocto] 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 at 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 at 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