From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/libtirpc: bump to version 0.3.2
Date: Fri, 24 Jul 2015 11:31:47 +0200 [thread overview]
Message-ID: <20150724113147.28d69deb@free-electrons.com> (raw)
In-Reply-To: <1437729695.20708.9.camel@embedded.rocks>
Dear J?rg Krause,
On Fri, 24 Jul 2015 11:21:35 +0200, J?rg Krause wrote:
> Sure. The problem is that with version 0.3.0 it was possible to disable
> auth DES optionally [1]. This was reverted in version 0.3.2 for
> backward compatibility with older glibc's. With commit
> 060b63865c58c716dc94c5987ab19b90899aa340 authdes_create() is defined by
> default in rpc_soc.c, which in return calls the undefined
> authdes_seccreate().
>
> My suggestion would be to remove authdes_create() in rpc_soc.c.
Where would authdes_seccreate() be normally implemented? For sure the
libtirpc developers didn't simply call an undefined function, no?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-24 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 6:38 [Buildroot] [PATCH v2 1/3] package/libtirpc: bump to version 0.3.2 Jörg Krause
2015-07-23 6:38 ` [Buildroot] [PATCH v2 2/3] package/libtirpc: fix musl build Jörg Krause
2015-07-23 6:38 ` [Buildroot] [PATCH v2 3/3] package/libtirpc: Do not build unsupported API files Jörg Krause
2015-07-23 21:06 ` [Buildroot] [PATCH v2 1/3] package/libtirpc: bump to version 0.3.2 Thomas Petazzoni
2015-07-24 7:17 ` Thomas Petazzoni
2015-07-24 9:21 ` Jörg Krause
2015-07-24 9:31 ` Thomas Petazzoni [this message]
2015-07-24 11:26 ` Jörg Krause
2015-07-24 11:43 ` Thomas Petazzoni
2015-07-24 12:27 ` Jörg Krause
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=20150724113147.28d69deb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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