From: Karel Zak <kzak@redhat.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: util-linux@vger.kernel.org
Subject: Re: Compile failure due to use of qsort_r
Date: Tue, 1 Apr 2014 15:45:17 +0200 [thread overview]
Message-ID: <20140401134517.GP23464@x2.net.home> (raw)
In-Reply-To: <CANyK_8d6L7vL6Mfq4VNdScjoVLb1K1+8hYsDnuQBZLOh5LC3BA@mail.gmail.com>
On Tue, Apr 01, 2014 at 01:03:10PM +0100, Paul Barker wrote:
> Hi all,
>
> I'm using util-linux as part of the OpenEmbedded build system and
> we've ran into two places where the use of qsort_r in util-linux is
> causing a compile failure:
>
> - CentOS 5.10 is using an old version of glibc which doesn't provide qsort_r
Well, I don't like this kind of arguments -- it's almost always
problematic to update only small subset of distro...
> - We're experimenting with musl-libc and this also doesn't provide qsort_r
This is better, I'll add #ifdef to the code. Thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-04-01 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 12:03 Compile failure due to use of qsort_r Paul Barker
2014-04-01 13:45 ` Karel Zak [this message]
2014-04-04 14:09 ` Karel Zak
2014-04-04 16:37 ` Paul Barker
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=20140401134517.GP23464@x2.net.home \
--to=kzak@redhat.com \
--cc=paul@paulbarker.me.uk \
--cc=util-linux@vger.kernel.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