NetBSD Problem Report #44613

From  Sun Feb 20 15:17:50 2011
Return-Path: <>
Received: from ( [])
	by (Postfix) with ESMTP id CF1AD63B100
	for <>; Sun, 20 Feb 2011 15:17:50 +0000 (UTC)
Message-Id: <>
Date: Sun, 20 Feb 2011 15:17:50 +0000 (UTC)
Subject: Tools pick up gsed from pkgsrc if installed
X-Send-Pr-Version: 3.95

>Number:         44613
>Category:       toolchain
>Synopsis:       Tools pick up gsed from pkgsrc if installed
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    toolchain-manager
>State:          analyzed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 20 15:20:01 +0000 2011
>Last-Modified:  Thu Jul 24 14:59:36 +0000 2014
>Originator:     Julio Merino
>Release:        NetBSD 5.1_STABLE
Julio Merino

System: NetBSD 5.1_STABLE NetBSD 5.1_STABLE (NBMAIL_DOMU) #1: Sat Dec 25 13:12:37 UTC 2010 amd64
Architecture: x86_64
Machine: amd64
	After removing the 'gsed' package from my system, I have realized that
	update builds on a previously-compiled release trees fail because they
	cannot find /usr/pkg/bin/gsed any more.

	The problem lies in that the configure scripts of several tools (e.g.
	src/tools/file/) look for a sed binary and stick its path into the
	generated 'libtool' script.  These tests only check for 'sed' and
	'gsed' and there is no sane way of overriding the names of the tools
	nor the paths they are looked for into.
	1) Install pkgsrc/textproc/gsed and ensure gsed is in your path
        2) tools
        3) grep -r gsed obj
	My naive attempt at adding SED=${HOST_SED:Q} to the CONFIGURE_ENV
	variables of Makefile.gnuhost and Makefile.gmakehost failed.  The
	offending configure scripts do not honor the SED variable.

	These configure scripts do honor defining a lt_cv_path_SED variable
	instead, but this is private.  I am not sure if we really want to
	override this variable with a valid path or attempt to do something
	else (hence why I am filing the PR instead of sending a fix).



State-Changed-From-To: open->feedback
State-Changed-When: Fri, 21 Sep 2012 01:01:52 +0000
julio, can you work on this?  setting the private variables is the "right"
way to handle this.  there usually aren't options for --path-to-sed etc.,
though upstream might be willing to add them.

State-Changed-From-To: feedback->analyzed
State-Changed-When: Thu, 24 Jul 2014 14:59:36 +0000
If the lack of reply in ~2 years didn't make it clear: no, I cannot work on this now.


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.