NetBSD Problem Report #34913

From chuck@xxx.pdl.cmu.edu  Wed Oct 25 18:38:17 2006
Return-Path: <chuck@xxx.pdl.cmu.edu>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id C1DBC63BA73
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 25 Oct 2006 18:38:16 +0000 (UTC)
Message-Id: <200610251838.k9PIc44L026643@xxx.pdl.cmu.edu>
Date: Wed, 25 Oct 2006 14:38:04 -0400 (EDT)
From: chuck@ece.cmu.edu
Reply-To: chuck@ece.cmu.edu
To: gnats-bugs@NetBSD.org
Subject: absolute paths from build machine in /var/db/libc.tags
X-Send-Pr-Version: 3.95

>Number:         34913
>Category:       lib
>Synopsis:       absolute paths from build machine in /var/db/libc.tags
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    lib-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 25 18:40:00 +0000 2006
>Originator:     Chuck Cranor
>Release:        NetBSD 3.0
>Organization:
pdl.cmu.edu
>Environment:

ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-3.0.1/i386/binary/sets/comp.tgz

>Description:

	the build process builds a ./var/db/libc.tags in the comp.tgz
	set with absolute path names from the build machine.   this 
	results in lines like this:

yp_unbind       /home/builds/ab/netbsd-3-0-1-RELEASE/src/lib/libc/yp/yplib.c    /^yp_unbind(dom)$/
yperr_string    /home/builds/ab/netbsd-3-0-1-RELEASE/src/lib/libc/yp/yperr_string.c     /^yperr_string(incode)$/
ypmatch_add     /home/builds/ab/netbsd-3-0-1-RELEASE/src/lib/libc/yp/yp_match.c /^ypmatch_add(map, key, keylen, val, vallen)$/
ypmatch_find    /home/builds/ab/netbsd-3-0-1-RELEASE/src/lib/libc/yp/yp_match.c /^ypmatch_find(map, key, keylen, val, vallen)$/
ypprot_err      /home/builds/ab/netbsd-3-0-1-RELEASE/src/lib/libc/yp/ypprot_err.c       /^ypprot_err(incode)$/



	I cannot see how this is useful, since most people will not
	have a /home/builds/ab/netbsd-3-0-1-RELEASE directory!



>How-To-Repeat:

	build NetBSD release.

>Fix:

	- sed it at build time into /usr/src and assume everyone is going 
	  to have a /usr/src directory (or symlink) that points to the 
	  right place.

	or 

	- put relative paths in the file and have some sort of
	  environment option that you can point at the source tree?

Home	PR Database Search