binaries linking errors

Wu Degang samuelandjw at gmail.com
Sun Jun 3 20:47:23 PDT 2012


On 4/6/12 11:29 AM, Jeremy Lavergne wrote:
>> 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?
>
I don't know what to expect. The following are the results:

wf112-026:~ wudegang$ du 
/opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o
8    
/opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o
wf112-026:~ wudegang$ otool -L 
/opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o
/opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o:


More information about the macports-users mailing list