From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Koen Kooi : mtd-utils: add 1.2.0+git for ubifs-support
Date: Fri, 16 Jan 2009 21:43:59 +0100 [thread overview]
Message-ID: <gkqrif$bjr$1@ger.gmane.org> (raw)
In-Reply-To: <20090116202514.GA24280@denix.org>
On 16-01-09 21:25, Denys Dmytriyenko wrote:
> On Sun, Jan 11, 2009 at 07:07:41PM +0100, Stefan Schmidt wrote:
>> Hello.
>>
>> On Sun, 2009-01-11 at 18:57, Stefan Schmidt wrote:
>>> On Sun, 2009-01-11 at 18:36, Koen Kooi wrote:
>>>> On 11-01-09 18:06, Stefan Schmidt wrote:
>>> Now the install of efsprogs-libs fails:
>>>
>>> | making install-shlibs in lib/et
>>> | make[1]: Entering directory
>>> `/home/stefan/Projekte/OpenEmbedded/build/openmoko/tmp/work/armv4t-angstrom-linux-gnueabi/e2fsprogs-libs-1.39-r1/e2fsprogs-libs-1.39/lib/et'
>>> | MKINSTALLDIRS /usr/lib /usr/lib
>>> | make[1]: MKINSTALLDIRS@: Command not found
>>>
>>> Do you use e2fsprogs-libs-1.42.2 or e2fsprogs-libs-1.39?
>> With 1.42.2 it works fine here. Bumped preferred version for the om stuff.
>
> First, the correct version is 1.41.2.
>
> Second, it looks like e2fsprogs-libs depends on gettext-native, otherwise it
> gives this nasty error message during do_configure:
>
> configure.in:545: error: possibly undefined macro: AM_GNU_GETTEXT
>
> Not many people see this issue, as their gettext-native is built earlly on.
>
The gettext thing has been fixed for a few days now.
regards,
Koen
next prev parent reply other threads:[~2009-01-16 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090111152021.47737188463@amethyst.openembedded.net>
2009-01-11 17:06 ` [oe-commits] Koen Kooi : mtd-utils: add 1.2.0+git for ubifs-support Stefan Schmidt
2009-01-11 17:36 ` Koen Kooi
2009-01-11 17:57 ` Stefan Schmidt
2009-01-11 18:07 ` Stefan Schmidt
2009-01-16 20:25 ` Denys Dmytriyenko
2009-01-16 20:43 ` Koen Kooi [this message]
2009-01-16 20:57 ` Denys Dmytriyenko
2009-01-16 21:01 ` Denys Dmytriyenko
2009-01-16 23:08 ` Tom Rini
2009-01-18 4:27 ` Denys Dmytriyenko
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='gkqrif$bjr$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.