From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] findutils: fix update-alternatives and native packages
Date: Wed, 23 Sep 2009 13:46:35 +0200 [thread overview]
Message-ID: <h9d1qs$564$1@ger.gmane.org> (raw)
In-Reply-To: <1253697229-6181-1-git-send-email-Martin.Jansa@gmail.com>
On 23-09-09 11:13, Martin.Jansa wrote:
> Move update-alternatives logic to findutils-alternatives.inc which is not included in -native packages.
> Patch mkinstalldirs.patch is needed also for findutils-native_4.2.29.
> Remove version 4.4 as there is no tarball upstream (it's 4.4.0 actually).
> Add latest version 4.4.2, probably not compatible with old glibc 2.6.1 (staging/armv4t-angstrom-linux-gnueabi/usr/include/stdio.h:654: error: conflicting types for 'rpl_fseeko'), findutils-native-4.4.2 is ok
Anything with rpl_* is usually a replacement function for the real
thing. I suspect the autoconf site files need updating to cope with
seeko. The iperf recipe has a tweak to avoid using rpl_malloc, maybe
something analogous can be done with findutils.
regards,
Koen
prev parent reply other threads:[~2009-09-23 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 9:13 [PATCH] findutils: fix update-alternatives and native packages Martin.Jansa
2009-09-23 11:46 ` Koen Kooi [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='h9d1qs$564$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox