NetBSD Problem Report #44953

From www@NetBSD.org  Wed May 11 08:58:26 2011
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id DBBB063C5D7
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 11 May 2011 08:58:25 +0000 (UTC)
Message-Id: <20110511085825.3D8CD63B95D@www.NetBSD.org>
Date: Wed, 11 May 2011 08:58:25 +0000 (UTC)
From: matthias.rampke@googlemail.com
Reply-To: matthias.rampke@googlemail.com
To: gnats-bugs@NetBSD.org
Subject: /usr/pkg/lib in default linker path causes configure errors
X-Send-Pr-Version: www-1.0

>Number:         44953
>Category:       pkg
>Synopsis:       /usr/pkg/lib in default linker path causes configure errors
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 11 09:00:01 +0000 2011
>Closed-Date:    Tue May 17 22:16:35 +0000 2011
>Last-Modified:  Tue May 17 22:16:35 +0000 2011
>Originator:     Matthias Rampke
>Release:        DragonFlyBSD 2.10 and 2.11
>Organization:
>Environment:
>Description:
Since a recent binutils upgrade DragonFly BSD includes /usr/pkg/lib in the default library search path. This causes some configure scripts to detect some installed libraries as present without them actually being buillink3ed in, see e.g. PRs pkg/44944 and pkg/44916. There is some discussion about this on the latter, but I open this PR so this can be discussed in general.

Since the headers are being shielded by the build wrappers, the build fails in these cases. 


>How-To-Repeat:
build mail/alpine on recent DragonFly with tcl installed and the

CONFIGURE_ARGS+=	--without-tcl

line removed from Makefile.
>Fix:
The question is, if and where this should be fixed. Options I see are:

1) Don't fix.
When problems with individual packages arise, the configure test can be forced, either unconditionally (as with pkg/44945) or with an option (as with pkg/44916) so the reliability and predictability of these packages actually increases.

2) Fix in DragonFly
Remove /usr/pkg/lib from default ld path, problem goes away for now - until some other OS decides to include it.

3) Fix in buildlink3
Find a way to reset the ld search path or specifically remove /usr/pkg/lib from it. Fixes this hole once and for all, but it's unsure if this is possible for any or all of the ld's out there.

>Release-Note:

>Audit-Trail:
From: "OBATA Akio" <obache@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/44953: /usr/pkg/lib in default linker path causes configure
 errors
Date: Wed, 11 May 2011 18:46:17 +0900

 On Wed, 11 May 2011 18:00:01 +0900, <matthias.rampke@googlemail.com> wrote:

 > 1) Don't fix.
 > When problems with individual packages arise, the configure test can be forced, either unconditionally (as with pkg/44945) or with an option (as with pkg/44916) so the reliability and predictability of these packages actually increases.

 I feel this approach should be preferred.
 Because this kind issues will always happen with builtin packages.

From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/44953: /usr/pkg/lib in default linker path causes configure
 errors
Date: Wed, 11 May 2011 12:48:38 +0200

 On Wed, May 11, 2011 at 09:00:01AM +0000, matthias.rampke@googlemail.com wrote:
 > 2) Fix in DragonFly
 > Remove /usr/pkg/lib from default ld path, problem goes away for now
 > - until some other OS decides to include it.

 This was only done to be "helpful" in first place, because someone
 decided it is a good idea if -L/usr/pkg/lib is good enough for linking
 custom software, but also including -R/usr/pkg/lib is not.

 There is no way to workaround this other than to kick out the custom
 DragonFly hacks in first place. Sorry, but this is a clear "Don't do
 that".

 Joerg

From: Thomas Klausner <wiz@NetBSD.org>
To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: pkg/44953: /usr/pkg/lib in default linker path causes configure
 errors
Date: Thu, 12 May 2011 10:53:52 +0200

 On Wed, May 11, 2011 at 09:00:01AM +0000, matthias.rampke@googlemail.com wrote:
 > 2) Fix in DragonFly
 > Remove /usr/pkg/lib from default ld path, problem goes away for now - until some other OS decides to include it.

 I agree with joerg. Please start a discussion on the DragonFly lists
 to remove this again.

 Thanks,
  Thomas

From: Matthias Rampke <matthias.rampke@googlemail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/44953: /usr/pkg/lib in default linker path causes configure errors
Date: Tue, 17 May 2011 21:46:40 +0200

 Fixed in DragonFly as of [1].

 [1] http://gitweb.dragonflybsd.org/dragonfly.git/commit/45bedb7267859396f5ece9106ced371b07297c57

State-Changed-From-To: open->feedback
State-Changed-By: wiz@NetBSD.org
State-Changed-When: Tue, 17 May 2011 22:05:54 +0000
State-Changed-Why:
Thanks for reporting that DragonFly changed it.
Is there anything left to do in this PR?


From: Matthias Rampke <matthias.rampke@googlemail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/44953 (/usr/pkg/lib in default linker path causes configure errors)
Date: Wed, 18 May 2011 00:10:02 +0200

 > Is there anything left to do in this PR?
 Nope, all clear.

State-Changed-From-To: feedback->closed
State-Changed-By: wiz@NetBSD.org
State-Changed-When: Tue, 17 May 2011 22:16:35 +0000
State-Changed-Why:
Fixed. Thanks for solving this upstream.


>Unformatted:

Home	PR Database Search