On Jun 8, 2004, at 11:46 AM, Armando Di Cianno wrote:
However, I have a recurring problem with frameworks -- I've seen this
problem in Addresses-0.4.5 and a CVS pull of gworkspace from today
(yeah, i know the ickiness of GWorkspace's Makefiles has been
addressed on discuss-gnustep, but it looks like they are fixed in
CVS). The problem is that the framework install
(/usr/GNUstep/Makefiles/Instance/framework.make in
internal-framework-install_:: tries to copy by tar cf - | tar xf -,
which is usually fine, and then some chown'ng magic, which is usually
fine, but I can only guess becuase of the sandboxing that I get errors
like these:
make[1]: Entering directory
`/var/tmp/portage/gworkspace-0.6.5_p060804/work/gworkspace/FSNode'
Making install for framework FSNode...
Creating
/var/tmp/portage/gworkspace-0.6.5_p060804/image//usr/GNUstep/System/
Library/Frameworks...
Installing framework FSNode...
tar: FSNode.framework/Versions/A/FSNode: Cannot change ownership to
uid 0, gid
0: No such file or directory
tar: FSNode.framework/Versions/A/libFSNode.so: Cannot change ownership
to uid 0, gid 0: No such file or directory
tar: Error exit delayed from previous errors
You could try adding
messages=yes
to the make command to get more information. The files that tar is
complaining about are links (I think), so perhaps tar is having
problems with the link not being there or the linked-to file not being
there or something. I'm not sure why this would happen though.
