From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Cc: Discussion of the angstrom distribution development
<angstrom-distro-devel@linuxtogo.org>
Subject: Re: Can't build on Fedora 13
Date: Sat, 24 Jul 2010 15:57:53 -0600 [thread overview]
Message-ID: <4C4B61E1.8080502@mlbassoc.com> (raw)
In-Reply-To: <AANLkTimJ7urU4OQ-1BXBJgU7SZFBRyw2D+Adzw-13eDa@mail.gmail.com>
On 07/24/2010 02:50 PM, Khem Raj wrote:
> On Sat, Jul 24, 2010 at 12:01 PM, Gary Thomas<gary@mlbassoc.com> wrote:
>> Trying to build angstrom-gnome-image for beagleboard, fresh checkout
>> of org.openembedded.dev:
>> commit 244deb462973a2d7a9bfcc3399843202f9d29d51
>> Author: Stanislav Brabec<utx@penguin.cz>
>> Date: Sat Jul 24 14:21:03 2010 +0000
>>
>> On Fedora 13, I get this error:
>>
>> ERROR: Function do_configure failed
>> NOTE: Task failed: ('function do_configure failed',
>> '/home/local/Angstrom_BeagleBoard/tmp/work/i686-linux/gawk-native-3.1.4-r3/temp/log.do_configure.10165')
>> ERROR: Logfile of failure stored in:
>> /home/local/Angstrom_BeagleBoard/tmp/work/i686-linux/gawk-native-3.1.4-r3/temp/log.do_configure.10165
>> Log data follows:
>> | automake (GNU automake) 1.11.1
>> | Copyright (C) 2009 Free Software Foundation, Inc.
>> | License GPLv2+: GNU GPL version 2 or later
>> <http://gnu.org/licenses/gpl-2.0.html>
>> | This is free software: you are free to change and redistribute it.
>> | There is NO WARRANTY, to the extent permitted by law.
>> |
>> | Written by Tom Tromey<tromey@redhat.com>
>> | and Alexandre Duret-Lutz<adl@gnu.org>.
>> | AUTOV is 1.11
>> | NOTE:
>> /home/local/Angstrom_BeagleBoard/tmp/sysroots/i686-linux/usr/share/gettext/config.rpath
>> not found. gettext is not installed.
>> | NOTE: Executing autoreconf --verbose --install --force --exclude=autopoint
>> -I
>> /home/local/Angstrom_BeagleBoard/tmp/work/i686-linux/gawk-native-3.1.4-r3/gawk-3.1.4/m4/
>> -I/home/local/Angstrom_BeagleBoard/tmp/sysroots/i686-linux/usr/share/aclocal-1.11
>> -I
>> /home/local/Angstrom_BeagleBoard/tmp/sysroots/i686-linux/usr/share/aclocal
>> | /usr/bin/autoreconf: unrecognized option `--exclude=autopoint'
>> | Try `/usr/bin/autoreconf --help' for more information.
>
> Why dont you stage autoconf-native and automake-native
An interesting question (that I don't know the answer to - I'm just a simple
user...)
A more interesting question is that I can see that all of these tools have been
built - my work tree shows:
autoconf-native-2.65-r9.0
automake-native-1.11.1-r3.0
gettext-native-0.18-r1
so why aren't they being used? I instrumented the do_configure script to show
which version of autoreconf was used and indeed it is /usr/bin/autoreconf!
>> | FATAL: autoreconf execution failed.
>> NOTE: package gawk-native-3.1.4-r3: task do_configure: Failed
>>
>> The same tree builds on Fedora 12
>>
>> Any ideas how to work past this?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2010-07-24 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 19:01 Can't build on Fedora 13 Gary Thomas
2010-07-24 19:19 ` Gary Thomas
2010-07-24 20:50 ` Khem Raj
2010-07-24 21:57 ` Gary Thomas [this message]
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=4C4B61E1.8080502@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=openembedded-devel@lists.openembedded.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.