NetBSD Problem Report #41275

From  Fri Apr 24 12:41:12 2009
Return-Path: <>
Received: from ( [])
	by (Postfix) with ESMTP id 4552063BC38
	for <>; Fri, 24 Apr 2009 12:41:12 +0000 (UTC)
Message-Id: <>
Date: Fri, 24 Apr 2009 12:41:11 +0000 (UTC)
Subject: installed lang/parrot references build directory
X-Send-Pr-Version: www-1.0

>Number:         41275
>Category:       pkg
>Synopsis:       installed lang/parrot references build directory
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    he
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 24 12:45:00 +0000 2009
>Closed-Date:    Sun May 15 01:03:27 +0000 2022
>Last-Modified:  Sun May 15 01:03:27 +0000 2022
>Originator:     Jörn Clausen
>Release:        NetBSD 4.0.1
University of Bielefeld
NetBSD hrzkpgsrc 4.0.1 NetBSD 4.0.1 (GENERIC) #0: Tue Oct  7 22:58:48 PDT 2008  builds@wb30:/home/builds/ab/netbsd-4-0-1-RELEASE/i386/200810080053Z-obj/home/builds/ab/netbsd-4-0-1-RELEASE/src/sys/arch/i386/compile/GENERIC i386

parrot_config from lang/parrot references its build directory:

$ parrot_config --dump | grep pkgsrc
build_dir => '/usr/pkgsrc/lang/parrot/work/parrot-1.0.0'
libparrot_ldflags => '-L/usr/pkgsrc/lang/parrot/work/parrot-1.0.0/blib/lib -lparrot'

"build_dir" is probably OK (this makes a build of Rakudo against this Parrot impossible, but that's mainly Rakudo's fault), but "libparrot_ldflags" looks just plain wrong.

In addition under Solaris, the variable "rpath_blib" references the build directory as well, similar to libparrot_ldflags.




Responsible-Changed-From-To: pkg-manager->he
Responsible-Changed-When: Fri, 24 Apr 2009 14:20:07 +0000
Over to maintainer.

State-Changed-From-To: open->feedback
State-Changed-When: Mon, 09 Nov 2009 07:05:02 +0000
The package has been updated several times in the last few months; does the
problem persist?

From: Havard Eidnes <>
Subject: Re: pkg/41275 (installed lang/parrot references build directory)
Date: Mon, 09 Nov 2009 10:05:47 +0100 (CET)

 > The package has been updated several times in the last few
 > months; does the problem persist?

 I suspect it does...  I've tried to bring this up in the parrot
 community, but they say something to the effect that "you're not
 supposed to use that config variable to get at the parrot lib",
 and for some reason they don't think that references to the build
 directory in "supposed not to be used" config variables is a bug.
 I tend to differ, but it looks like I'm losing that battle.

 See and

 Best regards,

 - H=E5vard

State-Changed-From-To: feedback->open
State-Changed-When: Sat, 28 Nov 2009 23:57:09 +0000
feedback received.

State-Changed-From-To: open->closed
State-Changed-When: Sun, 15 May 2022 01:03:27 +0000
The problem still exists today, but (a) it's an upstream issue,
(b) a workaround is in place, and (c) upstream continues to refuse
to fix it. More recent attempt:


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: gnats-precook-prs,v 1.4 2018/12/21 14:20:20 maya Exp $
$NetBSD:,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.