On May 10, 2010, at 8:12 AM, Mark J. Nelson wrote:

> On 05/10/10 08:01 AM, Rick McNeal wrote:
>> I'm trying to build ON from the sources and it looks like I've got
>> one last problem to resolve.
>> 
>> During the creation of the cpio archives I'm getting the following error:
>> 
>>    Failed to create generic usr archive: 483740 blocks
>>    cpiotranslate: usr/has/bin/pfksh: no packaging info
>> 
>> Now, the only place I can find pfksh referenced as package info is in
>> the pkg/manifests/{SUNWcs.mf,shell-ksh88.mf} files. I can probably
>> ignore the error since for my purposes I'm only going to using the
>> package files which have been created without error. I would like to
>> understand why I'm getting this error when clearly it's not
>> expected.
> 
> Hi, Rick--
> 
> Any chance that the pfksh in your proto area is from an older build?
> 

This is the second time I've done the build and I already thought that maybe I 
had some previous junk lying around. So, I removed archives, log, packages, and 
proto in my build area and then kicked the nightly off again.

> The usr/has/bin/pfksh object is currently produced by the closed build,
> and is not part of the closed bins tarball.  Which means that it
> shouldn't be in your proto area, unless it's leftover.
> 

Here I believe is the key. My source tree still has usr/src/cmd/pfexec and I 
looked at the install target which has the following:

    for s in $(BINSHELLS) ; do \
        $(RM) $(ROOTBIN)/pf$$s; \
        $(LN) $(ROOTBIN)/pfexec $(ROOTBIN)/pf$$s; \
    done

So, the error is not that pfksh is old junk in my tree, but that I somehow 
still have usr/src/cmd/pfexec in my tree which has been moved to the closed 
binary package. Do you concur?

> I bet removing it will fix your problem, and then you get bonus points
> if you can let me know where it came from (or confirm my suspicion.)
> 
> --Mark

----
Rick McNeal
rick.mcn...@lsi.com

“The government solution to any problem is usually at least as bad as the 
problem.” —Milton Friedman

_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org

Reply via email to