On 05/11/10 08:21 AM, Rick McNeal wrote: > > On 10-May-2010, at 11:06 AM, Mark J. Nelson wrote: > >> <clipping noise>
>> The fix should be to add usr/has/bin/pfksh to >> $CODEMGR_WS/exception_lists/packaging.open. >> >> If you confirm that takes care of your problem, I'll integrate it. It's >> possible that the link count may then be wrong for pfexec, and protocmp >> will complain. In that case, I'll figure out the best way to silence >> it, probably via an RFE against validate_pkg. We have one case of an >> isaexec hardlink to a closed binary that causes the same kind of >> warning, and it would be nice to get it cleaned up more generally. >> > > Adding pfksh to packaging.open prevented the cpio archive errror. Thank you. > I'm now getting the following warnings/errors during the build. The > first three don't seem like a big deal, but the error with in.iked is > worrisome because in.iked is an unknown binary. isaexec is 9072 bytes > and in.iked is 9376. The actual in.iked binaries which are found in > the architecture dependent directories are 330k (i86) and 403k > (amd64). Any ideas here? This is the problem that I mentioned above: "an isaexec hardlink to a closed binary that causes the same kind of warning." I should have been more specific. See below. > As I stated, for this build I removed the proto directory. But not the tools proto directory. :) > ==== Validating manifests against proto area ==== > > > Entries present in proto area but not manifests: > file opt/onbld/bin/bfudrop group=group mode=0555 owner=owner > path=opt/onbld/bin/bfudrop > file opt/onbld/bin/onblddrop group=group mode=0555 owner=owner > path=opt/onbld/bin/onblddrop > file opt/onbld/bin/sdrop group=group mode=0555 owner=owner > path=opt/onbld/bin/sdrop These three have legitimately been removed. You can cleanup usr/src/tools/proto/root_$MACH-nd to get rid of the warnings. > Entries that differ between manifests and proto area: > manifests hardlink path=usr/lib/inet/in.iked target=usr/lib/isaexec > proto area file usr/lib/inet/in.iked group=group mode=0555 owner=owner > path=usr/lib/inet/in.iked Because in.iked is produced by the closed build, you're not actually getting it from your build, so it is not being created as a hardlink to isaexec. But the packaging manifests expect it to be, as the first line indicates. Instead, it's coming from the closed-bins tarball, and it is extracted and created as a file. That's what the second line is telling you. This is something I would like to see cleaned up, but it has been relatively low priority. You may safely ignore the error. --Mark _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
