>Number:         9397
>Category:       pkg
>Synopsis:       cross m68k-netbsd package doesn't build
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager (NetBSD software packages system bug manager)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 11 19:54:00 2000
>Last-Modified:
>Originator:     Jason R. Thorpe
>Organization:
Numerical Aerospace Simulation Facility - NASA Ames
>Release:        Fri Feb 11 19:46:58 PST 2000
>Environment:
	
System: NetBSD dr-evil 1.4S NetBSD 1.4S (DR-EVIL) #323: Mon Feb 7 14:14:05 PST 2000 thorpej@dr-evil:/u1/netbsd/src/sys/arch/i386/compile/DR-EVIL i386


>Description:
	The pkgsrc/cross/m68k-netbsd does not build "out of the box".

	Errors as follows:

done
_muldi3
./libgcc2.c:41: stdlib.h: No such file or directory
./libgcc2.c:42: unistd.h: No such file or directory
In file included from ./libgcc2.c:48:
include/stddef.h:28: machine/ansi.h: No such file or directory
gmake: *** [libgcc2.a] Error 1
*** Error code 2

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
dr-evil:thorpej 20$

>How-To-Repeat:
	cd /usr/pkgsrc/cross/m68k-netbsd; make

>Fix:
	Clearly the cross packages want includes, etc. for the target
	to exist somewhere.  However, the package build mechanism doesn't
	take care of this for you, nor does it provide instructions on
	how to set it up for the package build to be happy.

	My application is to simply build kernels (a lot faster when you
	have to build a lot of them to test large changes to the kernel
	for "oops, doesn't compile" bugs).  I wouldn't mind a way to
	turn off the libgcc build altogether, since it's not needed for
	the kernel.

	In any case, the current situation is sub-optimal.  I suspect this
	exists for the powerpc-netbsd and sparc-netbsd targets as well.
>Audit-Trail:
>Unformatted: