[OpenAFS-devel] pinstall breaks fakeroot when compiling openafs for Nokia tablets

[Jason Edgecombe]

Hi everyone,

I'm trying get openafs to build for the latest OS update, diablo, on the
Nokia tablets. I'm getting the error "libfakeroot: FAKEROOTKEY not
defined in environment" . Marius was helpful on the maemo-developer list
for tracking the problem down to pinstall. pinstall is clobbering the
environment variables LD_PRELOAD and FAKEROOTKEY which are needed by
fakeroot.

Would someone enlighten me as to what pinstall does, why we use it, and
how to fix this?

More information is in the forwarded email below.

Thanks,
Jason

-------- Original Message --------
Subject: 	Re: libfakeroot: FAKEROOTKEY not defined in environment
Date: 	Thu, 17 Jul 2008 15:51:39 +0300
From: 	Marius Gedminas <marius@pov.lt>
To: 	maemo-developers@maemo.org
References: 	<487EAA30.2050002@rampaginggeek.com>



On Wed, Jul 16, 2008 at 10:10:56PM -0400, Jason Edgecombe wrote:
> I'm having some trouble with compiling openafs for diablo.
> 
> Here is the build log:
> https://garage.maemo.org/builder/diablo/openafs_1.4.7-3/armel.build.log.FAILED.txt
> 
> I get the error "libfakeroot: FAKEROOTKEY not defined in environment" 
> when trying to compile the package on my development box and when using 
> the autobuilder.

That error is printed by pinstall (or a subprocess, most likely cp) that
is a helper built in the same source tree.  I glanced at the source code
of pinstall, and I see that it execs /bin/cp (and strip) with an empty
environment.  That might explain why FAKEROOTKEY is lost.

On the other hand, I see in the log that pinstall was invoked
successfully a few times before the failure.  Also, if the environment
is empty, there's no LD_PRELOAD, therefore how would fakeroot's code
even get invoked to show the error message?

> I've tried running fakeroot beforehand and setting the FAKEROOTKEY 
> environment variable by hand, but I get the same error. Either both my 
> development machine (the vmware image from garage + diablo sdk) and the 
> autobuilder were set up wrong, or there is some error in my package.
> 
> BTW, the command I use to build the binary packages is 
> "dpkg-buildpackage -rfakeroot"
> 
> I appreciated any tips on how to fix this.

Marius Gedminas