From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] e2fsprogs_1.42.bb: Fix build fallout for uclibc
Date: Thu, 19 Jan 2012 08:42:46 -0800 [thread overview]
Message-ID: <4F184806.8040205@intel.com> (raw)
In-Reply-To: <74FB388C-DFB3-42A8-AAA3-C92B74433F9A@dominion.thruhere.net>
On 01/18/2012 05:34 AM, Koen Kooi wrote:
>
> Op 18 jan. 2012, om 10:51 heeft Koen Kooi het volgende geschreven:
>
>>
>> Op 18 jan. 2012, om 04:01 heeft Khem Raj het volgende geschreven:
>>
>>> e2fsprogs 1.42 onwards uses fallocate() which uclibc
>>> does not implement(yet). In most of places its use
>>> is controlled and it only used when configure detects
>>> fallocate being present but in this one case it missed
>>> to check for fallocate being available so here we
>>> add the check
>>
>> FWIW, e2fsprogs(-native) also has problems with ASNEEDED:
>>
>> | tune2fs: symbol lookup error: tune2fs: undefined symbol: ext2fs_group_desc
>
> And that one suddenly went away!
That was fixed when the bitbake.conf change made it into master which
now adds base_libdir_native to the RPATH for native compiled binaries.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=35759f977eec6ef81e125a509a7148d7e53a6515
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-01-19 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 3:01 [PATCH] e2fsprogs_1.42.bb: Fix build fallout for uclibc Khem Raj
2012-01-18 9:51 ` Koen Kooi
2012-01-18 13:34 ` Koen Kooi
2012-01-19 16:42 ` Scott Garman [this message]
2012-01-19 19:56 ` Saul Wold
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=4F184806.8040205@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@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.