From darius@holly.dons.net.au  Tue Jan 26 02:00:34 1999
Received: from holly.dons.net.au (holly.dons.net.au [203.31.81.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08388
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 26 Jan 1999 02:00:32 -0800 (PST)
          (envelope-from darius@holly.dons.net.au)
Received: (from root@localhost)
	by holly.dons.net.au (8.9.2/8.8.8) id UAA23455;
	Tue, 26 Jan 1999 20:30:28 +1030 (CST)
	(envelope-from darius)
Message-Id: <199901261000.UAA23455@holly.dons.net.au>
Date: Tue, 26 Jan 1999 20:30:28 +1030 (CST)
From: "Daniel J. O'Connor" <darius@holly.dons.net.au>
Reply-To: darius@holly.dons.net.au
To: FreeBSD-gnats-submit@freebsd.org
Subject: a typo in /usr/obj/aout/usr/src/tmp/usr/include/sys/elf_common.h
X-Send-Pr-Version: 3.2

>Number:         9695
>Category:       bin
>Synopsis:       a typo in /usr/obj/aout/usr/src/tmp/usr/include/sys/elf_common.h
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 26 02:10:02 PST 1999
>Closed-Date:    Sat Aug 21 21:00:47 PDT 1999
>Last-Modified:  Sat Aug 21 21:03:46 PDT 1999
>Originator:     Daniel J. O'Connor
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
>Environment:
Doing make aout-to-elf-build on a 3.0-current (on the 12th of Jan 99), with
-current sources as of the 26th of Jan.

>Description:
The file /usr/obj/aout/usr/src/tmp/usr/include/sys/elf_common.h has '#defmne'
on line 101 instead of '#define' but /usr/src/sys/sys/elf_common.h is fine.
Hmm :-/

>How-To-Repeat:
Do aout-to-elf-build on today's 4.0

>Fix:
Hmm.. well it could be NFS problem, so maybe a little hard to fix from this.


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: hoek 
State-Changed-When: Sat Aug 21 21:00:47 PDT 1999 
State-Changed-Why:  
Hmmm....  Well, if it's not a typo in the source file, there isn't too much 
we can do about this problem.  Try again.  If it was NFS, then I'll note 
that many NFS problems have been fixed.  In the more likely case that it's 
bad hardware, somewhere, then the problem should either disappear or  
reappear somewhere else in a more or less random fashion.  Good luck. 
>Unformatted:
