Subject: pkg/25584: GNUstep packages can't be built using ccache
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <jmmv@menta.net>
List: pkgsrc-bugs
Date: 05/15/2004 23:51:30
>Number:         25584
>Category:       pkg
>Synopsis:       GNUstep packages can't be built using ccache
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 15 21:52:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Julio M. Merino Vidal
>Release:        NetBSD 2.0E
>Organization:
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/
>Environment:
	
	
System: NetBSD dawn.local 2.0E NetBSD 2.0E (DAWN) #0: Fri May 14 20:45:04 CEST 2004 jmmv@dawn.local:/home/build/obj/usr/src/sys/arch/i386/compile/DAWN i386
Architecture: i386
Machine: i386
>Description:
        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).

>How-To-Repeat:
        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
        abort configuration.

>Fix:
	Not provided.
>Release-Note:
>Audit-Trail:
>Unformatted: