[Slackbuilds-users] EncFS requres boost <= 1.41

Niels Horn niels.horn at gmail.com
Fri Jun 4 22:47:35 UTC 2010

On Fri, Jun 4, 2010 at 7:21 PM, Ben Mendis <dragonwisard at gmail.com> wrote:
> On Fri, Jun 4, 2010 at 5:44 PM, Niels Horn <niels.horn at gmail.com> wrote:
>> 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
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
> This is exactly why I wrote to the list. I didn't realize until after
> upgrading to 13.1 that I wouldn't be able to access my encrypted files. (And
> those files are pretty important to me...which is why they were encrypted in
> the first place.) I still have Slackware 13.0 in a VM that I can use to
> decrypt the folders, but that's really cumbersome and I was hoping someone
> might know an easier and more permanent solution.

Well, my "hack" might not be the "easier" solution you are looking
for, but it might be a way to keep things working until upstream
solves the issue.
But you will need some knowledge about static linking etc.
Nothing that can't be learned by Googling though if you have some
basic experience with gcc and compiling software.


More information about the SlackBuilds-users mailing list