[maemo-developers] libfakeroot: FAKEROOTKEY not defined in environment

[From: Marius Gedminas]

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
-- 
If the code and the comments disagree, then both are probably wrong.
                -- Norm Schryer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.maemo.org/pipermail/maemo-developers/attachments/20080717/d241b263/attachment.pgp