[19250] in Kerberos_V5_Development
Re: krb5.conf and 32 vs 64-bit plugins
daemon@ATHENA.MIT.EDU (Tomas Kuthan)
Mon Aug 17 12:22:59 2015
Message-ID: <55D20A53.3070506@oracle.com>
Date: Mon, 17 Aug 2015 18:22:43 +0200
From: Tomas Kuthan <tomas.kuthan@oracle.com>
MIME-Version: 1.0
To: Russ Allbery <eagle@eyrie.org>
In-Reply-To: <87bne6aps6.fsf@hope.eyrie.org>
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 08/17/15 05:38 PM, Russ Allbery wrote:
> Tomas Kuthan <tomas.kuthan@oracle.com> writes:
>
>> Just to clarify, with this proposal we are trying to address plugins in
>> non-default library path (I should have made up a better example, such
>> as "/opt/vendor/product/version/lib/plugins/$ISA/"). Default library
>> path already works fine for both 32 and 64-bit.
>
>> How about supporting the following macros, that would be settable at
>> configure with the following default values:
>
>> #define ISA_STRING "/$ISA/"
>> #define ISA_32 "/"
>> #define ISA_64 "/64/"
>
>> I believe this should offer enough flexibility.
>
> This wouldn't work for Debian and Debian-derived systems that support full
> multiarch, not just the biarch system that Red Hat initially implemented.
>
> The variation that probably would work for those systems would be to allow
> the expansion of $ISA to be defined at compile time, so that on Debian
> amd64 (for example) it would be defined as "/x86_64-linux-gnu/". But that
> probably wouldn't be enough for Solaris, where you want to search multiple
> paths.
>
Hi Russ,
thank you for the pointer to the multiarch paradigm.
I guess that's back to the drawing board for me :-)
Tomas
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
