[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Monday 29 August 2005 8:57 pm, Grant Sewell wrote: > > done > > cp: `./ChangeLog' and `../qof-0.6.0/po/ChangeLog' are the same file > > cp: `./Makefile.in.in' and `../qof-0.6.0/po/Makefile.in.in' are the same > > file cp: `./POTFILES.in' and `../qof-0.6.0/po/POTFILES.in' are the same > > file cp: `./Makevars' and `../qof-0.6.0/po/Makevars' are the same file > > make[1]: *** [distdir] Error 1 > > make[1]: Leaving directory `/opt/working/qof/po' > > make: *** [distdir] Error 1 > > > > The files really do appear the same - deleting one allows the copy to > > take place but the next make dist breaks it again. > > But they really are the same file, and not a symlink either: > > > > Are they *actually* the same file? A hardlink perhaps, or just two > completely identical files? Identical files would have a different INODE and could be copied in place easily. (Copy the same file to a new directory and then copy it over itself again and again - an identical file is not an error.) No, these are hard links, created by the build process. The problem is WHY there is an existing file in the way. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpGl8IYV1Lq4.pgp
Description: PGP signature