Subject: toolchain/25565: Can't build tools for -current.
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <rkr@olib.org>
List: netbsd-bugs
Date: 05/14/2004 10:48:30
>Number:         25565
>Category:       toolchain
>Synopsis:       Can't build tools for -current.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    toolchain-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 14 10:49:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Richard Rauch
>Release:        NetBSD/amd64
>Organization:
n/a
>Environment:
NetBSD socrates 2.0E NetBSD 2.0E (socrates) #11: Mon May  3 23:36:31 CDT 2004  root@socrates:/usr/netbsd/ucrrent/src/sys/arch/amd64/compile/obj.amd64/socrates amd64

(Sorry if there are typos.  The system appears to require some minor
change for sending email, and links-gui (just rebuilt) no longer lets
me paste into input forms.)
>Description:
When I try to build a new set of tools (I have upgraded my sources,
in the hope of getting a stable kernel), I am eventually greeted with
this:

*** Configuration unknown-unknown-netbsd2.0E not supported
Configure in /usr/netbsd/current/src/tools/gcc/obj.amd64/build/gcc failed, exiting.


I thought that it might have been caused by some cruft from a prior
build on LINUX (the source tree is NFS mounted).  I tried cleaning
the source tree.  I even tried deleting the whole tree and re-CVSing
the sources.

/etc/mk.conf has:

X11SRCdir=/usr/netbsd/current/xsrc
PREFER_NATIVE=Xft Xrandr Xrender expat fontconfig \
  freetype2 glu randrext render xcuursor yes
PREFER_PKGSRC= no

MPLAYER_DISABLE_DRIVERS= arts
OBJMACHINE= yes
PKGSRC_MESSAGE_RECIPIENT=rkr
BLENDER_USE_EXPYTHON=YES
BLENDER_INSTALL_DOC=YES
PAPERSIZE=Letter
USE_TETEX2=YES
FAILOVER_FETCH=YES

ACCEPTABLE_LICENSES+=povray-license


(Again, sorry if there are typos.  Obviously, most of mk.conf relates to
pkgsrc.)


Installing a 2.0 release candidate or a -current snapshot is not a real
option since the GENERIC kernel has IOAPIC turned on, and that in turn
effectively prevents me from using the machine.  (Depending on what's
plugged in where, various devices lose touch with their interrupt
handlers.  USB mice die and won't recover without a reboot.  Ethernet
cards never work at all, etc.  There is an outstanding PR on that.
The system *works*, but is of limited use without ethernet, etc.
(^&)
>How-To-Repeat:
On my NetBSD/amd64 system, attempt to build the tools for -current.
>Fix:
Dunno.
>Release-Note:
>Audit-Trail:
>Unformatted: