binaries linking errors

[Jeremy Lavergne]

> After a upgrade outdated operation, I got the following messages in the end:
> 
> --->  Scanning binaries for linking errors: 39.9%
> Warning: Error parsing file /opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o: Premature end of data, possibly corrupt file
> --->  Scanning binaries for linking errors: 39.9%
> Warning: Error parsing file /opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/static/crt3.o: Premature end of data, possibly corrupt file
> --->  Scanning binaries for linking errors: 100.0%
> --->  No broken files found.
> 
> How should I interpret them? Do I need to worry about them? What should I do with them?

I would check their sizes with the `du` command:
du /opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o

Let us know if they actually contain data. You might also be able to run `otool -L` against them:
otool -L /opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o

Maybe someone knows if these are being linked against from a binary or if they're the actual binaries being scanned?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 8796 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20120603/dff1e0b3/attachment.bin>