arm/181220: make xdev for arm installation fails

Ian Lepore ian at FreeBSD.org
Sun Aug 11 14:20:01 UTC 2013


The following reply was made to PR arm/181220; it has been noted by GNATS.

From: Ian Lepore <ian at FreeBSD.org>
To: Christopher Abbey <rissicay at gmail.com>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: arm/181220: make xdev for arm installation fails
Date: Sun, 11 Aug 2013 08:13:26 -0600

 On Sun, 2013-08-11 at 01:20 +0000, Christopher Abbey wrote:
 > >Number:         181220
 > >Category:       arm
 > >Synopsis:       make xdev for arm installation fails
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-arm
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sun Aug 11 01:30:00 UTC 2013
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Christopher Abbey
 > >Release:        9.1
 > >Organization:
 > >Environment:
 > FreeBSD robolace.localdomain 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec  4 09:23:10 UTC 2012     root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 > 
 > >Description:
 > When building xdev:
 >     make XDEV=arm XDEV_ARCH=armv6 xdev
 > 
 > It fails with the output:
 > 
 > set -e; cd /usr/src/include; make buildincludes; make installincludes
 > creating osreldate.h from newvers.sh
 > *** [osreldate.h] Error code 1
 > 
 > Stop in /usr/src/include.
 > *** [includes] Error code 1
 > 
 > Stop in /usr/src/include.
 > *** [include.includes__D] Error code 1
 > 
 > Stop in /usr/src.
 > *** [_xi-includes] Error code 1
 > 
 > Stop in /usr/src.
 > *** [xdev] Error code 1
 > 
 > Stop in /usr/src.
 > 
 > 
 > The problem file appears to be:
 > /usr/src/sys/conf/newvers.sh
 > 
 > It looks like ${0} is printing sh instead of the script name
 > [snip]
 
 There were two checkins yesterday that appear to be potential fixes for
 this problem, r254184 and r254217.  Could you please apply those and see
 if it fixes the problem without hard-coding a pathname?
 
 -- Ian
 
 


More information about the freebsd-arm mailing list