binaries linking errors

[Wu Degang]

On 4/6/12 9:05 PM, Clemens Lang wrote:
> On Mon, Jun 04, 2012 at 11:47:23AM +0800, Wu Degang wrote:
>>> Maybe someone knows if these are being linked against from a binary
>>> or if they're the actual binaries being scanned?
> rev-upgrade scans all files that file(1) would identify as Mach-O
> (binary or library). Usually, .o files should not mach this filter, but
> apparently occasionally some still do.
>
> You can safely ignore the warning.
>
>> 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:
> Do you mind running hexdump on this file and pasting the output? I'd
> like to find out why an object file is considered binary (that is, why
> an object file contains the Mach-O header).
>
Not at all. The following is the output:

bash-3.2$ hexdump 
/opt/local/lib/apple-gcc40/lib/gcc/i686-apple-darwin11.3.0/4.0.1/kext/crt3.o
0000000 ce fa ed fe 07 00 00 00 03 00 00 00 01 00 00 00
0000010 01 00 00 00 7c 00 00 00 00 20 00 00 01 00 00 00
0000020 7c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000030 00 00 00 00 00 00 00 00 00 00 00 00 98 00 00 00
0000040 00 00 00 00 07 00 00 00 07 00 00 00 01 00 00 00
0000050 00 00 00 00 5f 5f 74 65 78 74 00 00 00 00 00 00
0000060 00 00 00 00 5f 5f 54 45 58 54 00 00 00 00 00 00
0000070 00 00 00 00 00 00 00 00 00 00 00 00 98 00 00 00
0000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80
*
0000090