From nobody@FreeBSD.org  Sun Jun  5 21:25:39 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EE05F16A41C
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  5 Jun 2005 21:25:39 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CD2E843D49
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  5 Jun 2005 21:25:39 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j55LPd04016187
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 5 Jun 2005 21:25:39 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j55LPd6E016186;
	Sun, 5 Jun 2005 21:25:39 GMT
	(envelope-from nobody)
Message-Id: <200506052125.j55LPd6E016186@www.freebsd.org>
Date: Sun, 5 Jun 2005 21:25:39 GMT
From: Kyryll A Mirnenko <mirya@matrix.ua>
To: freebsd-gnats-submit@FreeBSD.org
Subject: libtool15 won't work if not in same FS with ports
X-Send-Pr-Version: www-2.3

>Number:         81930
>Category:       ports
>Synopsis:       libtool15 won't work if not in same FS with ports
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jun 05 21:30:03 GMT 2005
>Closed-Date:    Tue Jun 07 21:06:38 GMT 2005
>Last-Modified:  Wed Jun  8 08:40:07 GMT 2005
>Originator:     Kyryll A Mirnenko
>Release:        RELENG_5_4
>Organization:
matrix.ua
>Environment:
FreeBSD localhost 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #41: Sun May 15 17:28:00 EEST 2005     root@localhost:/usr/src/sys/i386/compile/M
Y-O3  i386 
>Description:
      If ports tree is placed in separate FS libtool15 (maybe 13 too) fails to operate 'cause of improper `ln` (for hard link) usage in line 1137:

if test "$need_locks" = yes; then
      until $run ln "$progpath" "$lockfile" 2>/dev/null; do
#                ^ here
        $show "Waiting for $lockfile to be removed"
        sleep 2
      done

>How-To-Repeat:
      Put ports into separate FS & try to build smth using libtool. It fails to create a .lock file
>Fix:
      use `ln -s` or whatever else there :)
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: pav 
State-Changed-When: Tue Jun 7 21:05:29 GMT 2005 
State-Changed-Why:  
Can't reproduce: compiling port on NFS mount, libtool15 is on local UFS /usr, works. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=81930 

From: Kyryll A Mirnenko <mirya@matrix.kiev.ua>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: ports/81930: libtool15 won't work if not in same FS with ports
Date: Wed, 08 Jun 2005 11:28:20 +0300

 The line specified makes `ln /usr/local/bin/libtool15 ./my.lock`, which 
 is surely invalid across FS. Ensure the statement is reached in you case 
 (`if test "$need_locks" = yes; then`), e.g. put a "breakpoint" there & 
 retry, for me it is (so I see "Waiting for $lockfile to be removed" 
 repeated endlessly). $need_locks seems to be the key
>Unformatted:
