Subject: bin/14162: unexpected toolchain build behavior if USE_NEW_TOOLCHAIN
To: None <gnats-bugs@gnats.netbsd.org>
From: None <thorpej@shagadelic.org>
List: netbsd-bugs
Date: 10/05/2001 11:35:38
>Number: 14162
>Category: bin
>Synopsis: unexpected toolchain build behavior if USE_NEW_TOOLCHAIN
>Confidential: yes
>Severity: critical
>Priority: high
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Oct 05 11:36:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Jason R Thorpe
>Release: NetBSD 1.5Y, Oct 5 2001
>Organization:
Wasabi Systems, Inc.
>Environment:
System: NetBSD cp1500-1.fast-100.shagadelic.org 1.5Y NetBSD 1.5Y (SHAG-CP1500) #6: Fri Oct 5 10:37:00 PDT 2001 thorpej@cp1500-1.fast-100.shagadelic.org:/nfs-yeah-baby-u1/netbsd/src/sys/arch/sparc64/compile/SHAG-CP1500 sparc64
Architecture: sparc64
Machine: sparc64
>Description:
The ability to build individual toolchain programs for
non-tools use (i.e. the native tools for the target system)
seems to no longer work .. it only works if you build from
the top-level.
>How-To-Repeat:
On a system that uses USE_NEW_TOOLCHAIN (I noticed this on
a sparc64 system):
cp1500-1:thorpej 19$ pwd
/usr/src/gnu/usr.bin/binutils
cp1500-1:thorpej 20$ sudo make
cp1500-1:thorpej 21$
This is .. counter-intuitive, to say the least, and somewhat
annoying if you're trying to fix warnings in a program so that
the build can complete.
>Fix:
Not provided.
>Release-Note:
>Audit-Trail:
>Unformatted: