Re: gworkspace build error

[Nicola Pero]

On Thu, 10 Oct 2002, Matthias Klose wrote:

> Hi,
> 
> Debian builds its packages by auto builders in a restricted
> environment. Currently gworkspace fails to build on arm and m68k
> (currently I cannot see, why the builds do not fail on other
> architectures). See
> 
> http://buildd.debian.org/fetch.php?&pkg=gworkspace&ver=0.4.1-0.1&arch=m68k&stamp=1034211972&file=log&as=raw
> 
> The build fails at:
> 
>  Linking app GWorkspace ...
> /usr/lib/GNUstep/System/Makefiles/mkinstalldirs GWorkspace.app/Resources
> mkdir -p GWorkspace.app/Resources
> 2002-10-10 03:02:31.788 plmerge[316] parent directory of lock file 
> '/root/GNUstep/Defaults/.GNUstepDefaults.lck' is not writable
> plmerge: Uncaught exception NSInvalidArgumentException, reason: nil argument 
> for timeIntervalSinceDate:
> make[3]: *** [GWorkspace.app/Resources/Info-gnustep.plist] Error 1
> make[2]: *** [GWorkspace.all.app.variables] Error 2
> make[2]: Leaving directory `/build/buildd/gworkspace-0.4.1/GWorkspace'
> make[1]: *** [internal-all] Error 2
> make[1]: Leaving directory `/build/buildd/gworkspace-0.4.1'
> 
> So it seems that gworkspace tries to write into the gnustep user
> dir during the build. Is this special to gworkspace, or a bug/feature
> in gnustep-make? How can I avoid it?

Good question.

Maybe you can change the location of the user defaults in the restricted
environment during the build (it should be possible by adding a .GNUsteprc
in the user dir, or if you can't add a file in your home dir, by adding a
.GNUsteprc in the GNUSTEP_SYSTEM_ROOT).