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

[From: Jason Edgecombe]

Jason Edgecombe wrote:
> Marius Gedminas wrote:
>   
>> 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.
>>>     
>>>       
> ok, this just gets weirder. According to Marius' conclusion, pinstall 
> should always fail because it clobbers the environment, but it works 
> after I switch to the CHINOOK_ARMEL scratchbox target. It breaks when I 
> switch back to the DIABLO_ARMEL target.
>   
FYI, the solution was what Marius suggested. I tweaked the pinstall 
command to not clobber the environment.

Jason