[Slackbuilds-users] EncFS requres boost <= 1.41

[Niels Horn]

On Fri, Jun 4, 2010 at 6:36 PM, Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> On Friday 04 June 2010 23:32:24 Niels Horn wrote:
>> On Fri, Jun 4, 2010 at 6:06 PM, Ben Mendis <dragonwisard at gmail.com> wrote:
>> > Since I was already using EncFS in 13.0 I went ahead and tried to compile
>> > it for 13.1. There's one "invalid conversion from 'const char*' to
>> > 'char*'" error to fix, but even after fixing that the resulting binary
>> > doesn't work. Apparently the problem is that Slackware 13.1 has upgraded
>> > to boost 1.42.0 and encfs requires 1.41 or earlier.
>> >
>> > See: http://code.google.com/p/encfs/issues/detail?id=60
>> >
>> > Therefore my question is, is it feasible to install boost-1.41
>> > side-by-side with the boost-1.42 provided by Slackware?
>> > Does anyone have any advice on how this can be resolved?
>>
>> Ouch... Just read the posts on that page. Sounds like a really ugly
>> situation to me.
>>
>> I think a solution could be statically linking the "old" boost library
>> into EncFS.
>> But I haven't tried this (and don't have time to try it in the
>> foreseeable future), so YMMV...
>>
>> Side-by-side installation of the two boost versions is a guarantee to
>> other problems IMHO.
>
> IMHO this is clearly a case where waiting for upstream to fix it is the most
> feasible option. The boost bugreport
> (https://svn.boost.org/trac/boost/ticket/3990) clearly states the fix needs to
> be in encfs. Until the fix is available I'm not going to submit encfs for 13.1
> (no matter what hack might be suggested as a "solution").
>
> Grs,
> Heinz
>

Heinz,

I agree that upstream should fix this, but reading the posts from both
sides it might take a while before one of them gives in and admits
that they should act. :)

My "solution" (OK, it's more of a hack...) was suggested thinking of
situations where people _need_ to get EncFS running on 13.1 to access
data etc...
Not a solution for the SlackBuild, definitely!

Niels