So gcc finally finished, and I got the same error. Here's the output as requested:
dpkg-deb -b root-gcc4-4.1.9999-20060617 /sw/fink/10.4/unstable/main/ binary-darwin-powerpc/languages dpkg-deb: building package `gcc4' in `/sw/fink/10.4/unstable/main/ binary-darwin-powerpc/languages/gcc4_4.1.9999-20060617_darwin- powerpc.deb'. tar: ./sw/lib/gcc4/include/c++/4.2.0/powerpc-apple-darwin8/bits/stdc+ +.h.gch/O0g.gch: file changed as we read it ===== Old ctime: 1173001850 0 New ctime: 1173002170 0 Old size : 0 19216528 New size : 0 19216528 ===== /sw/bin/dpkg-deb: subprocess tar -cf returned error exit status 1 ### execution of dpkg-deb failed, exit code 2 Removing runtime build-lock... Removing build-lock package... /sw/bin/dpkg-lockwait -r fink-buildlock-gcc4-4.1.9999-20060617 (Reading database ... 45240 files and directories currently installed.) Removing fink-buildlock-gcc4-4.1.9999-20060617 ... Failed: can't create package gcc4_4.1.9999-20060617_darwin-powerpc.deb hth, - Koen. On Mar 3, 2007, at 3:52 AM, Martin Costabel wrote: > Could those of you who have or had the dpkg-deb failure caused by > tar-1.16.1 claiming > > "file changed as we read it" > > please help with debugging this? Based on the outcome of these > tests, we should be able to decide whether we need to patch tar or > dpkg, or whether we need to dig further down. > > I have made a special version of the tar executable that prints > some more information if this error appears. It prints the old/new > ctimes and the old/new file sizes. The special version is a > universal binary (so it should work on both ppc and intel) and is > available at http://perso.orange.fr/costabel/tar.gz > > A possible test procedure to follow would be: > > 1. Download the new tar: > > curl -O http://perso.orange.fr/costabel/tar.gz > gunzip tar.gz > chmod +x tar > mv tar /var/tmp/ > > 2. Replace (temporarily) Fink's tar by the new one > > sudo ln -sf /var/tmp/tar /sw/bin/tar > > 3. Build one of the packages that give you the tar error (mysql, > gcc42, gnumeric were among those where the error was reported). > Cross your fingers that the error will happen again ;-) > > 4. Report to the list the part of the error message that is printed > after the "file changed as we read it" line. > > 5. Put Fink's tar back to where it was before > > sudo ln -sf gtar /sw/bin/tar > > Thanks > > -- > Martin > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
