Subject: pkg/25584: GNUstep packages can't be built using ccache
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <firstname.lastname@example.org>
Date: 05/15/2004 23:51:30
>Synopsis: GNUstep packages can't be built using ccache
>Arrival-Date: Sat May 15 21:52:00 UTC 2004
>Originator: Julio M. Merino Vidal
>Release: NetBSD 2.0E
Julio M. Merino Vidal <email@example.com>
The NetBSD Project - http://www.NetBSD.org/
System: NetBSD dawn.local 2.0E NetBSD 2.0E (DAWN) #0: Fri May 14 20:45:04 CEST 2004 firstname.lastname@example.org:/home/build/obj/usr/src/sys/arch/i386/compile/DAWN i386
The gnustep* packages can't be built when using ccache as the compiler,
i.e, setting PKGSRC_COMPILER="ccache gcc". I guess the same problem
will appear if using distcc.
The problem is that the configure script enters an infinite loop when
calling the compiler, driving to a 'cannot fork' error that ends up
with 'the compiler is broken'.
I think this happens in these packages because they change PATH's
value directly. Buildlink3 and compiler.mk are very path sensible,
so any differences in there can lead to problems. (Just a guess).
Set PKGSRC_COMPILER="ccache gcc" in the environment and try to build
devel/gnustep-make, for example. It will consume lots of CPU and then