Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jun 2011 14:01:28 -0700
From:      Doug Barton <dougb@FreeBSD.org>
To:        Sunpoet Po-Chuan Hsieh <sunpoet@freebsd.org>
Cc:        jhell <jhell@DataIX.net>, FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   Re: shells/ksh93 install fail
Message-ID:  <4E025828.1020702@FreeBSD.org>
In-Reply-To: <20110622202809.GA92250@bonjour.sunpoet.net>
References:  <4E00F5A9.6040900@FreeBSD.org> <20110621200214.GB62312@DataIX.net> <4E00FDD7.3060204@FreeBSD.org> <20110622202809.GA92250@bonjour.sunpoet.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 6/22/2011 1:28 PM, Sunpoet Po-Chuan Hsieh wrote:
> On Tue, Jun 21, 2011 at 01:23:51PM -0700, Doug Barton wrote:
>> On 6/21/2011 1:02 PM, jhell wrote:
>>>
>>>
>>> On Tue, Jun 21, 2011 at 12:48:57PM -0700, Doug Barton wrote:
>>>> An effort to upgrade to 20110208_1 is failing for me:
>>>>
>>>> ===>    Installing for ksh93-20110208_1
>>>> ===>     Generating temporary packing list
>>>> ===>    Checking if shells/ksh93 already installed
>>>> install   -o root -g wheel -m 555
>>>> /usr/local/tmp/usr/ports/shells/ksh93/work/bin/ksh /usr/local/bin/ksh93
>>>> install: $WRKDIRPREFIX/usr/ports/shells/ksh93/work/bin/ksh: No such file
>>>> or directory
>>>> *** Error code 71
>>>>
>>>> Is it possible that $WRKDIRPREFIX is the trigger?
>>>>
>>>
>>> I did not actually see that here on 8-STABLE/i386, just for the record.
>>
>> Thanks. At least one person on IRC said that it worked for them with
>> or without $WRKDIRPREFIX, so that's probably not it. What's odd is
>> that these package building systems have been working fine for
>> hundreds of ports for quite a while now, so I'm stumped.
>
> Hi Doug,
>
> I have WRKDIRPREFIX=/usr/ports/works in /etc/make.conf. I'm running a
> 8-STABLE amd64. Do you need me to generate a build log for you to
> further investigate this problem?
>
> BTW, did you run 'find' to search for ksh? The binary must be somewhere
> in the WRKSRC. It might be helpful to know the path of ksh.

It didn't exist at all. However I think I found the problem. If I remove 
the STATIC option everything goes as planned. Perhaps that gives you a 
new area to examine?


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E025828.1020702>