Bug 47 - File in worng format libc.so.o
Summary: File in worng format libc.so.o
Status: CLOSED INVALID
Alias: None
Product: uClibc
Classification: Unclassified
Component: Shared Library Support (show other bugs)
Version: 0.9.30
Hardware: PC Linux
: P5 major
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-15 02:14 UTC by Mark
Modified: 2009-03-03 00:21 UTC (History)
4 users (show)

See Also:
Host: i686-pc-linux-gnu
Target: arm-cb-linux-uclibc
Build: i686-pc-linux-gnu

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark 2009-01-15 02:14:32 UTC 
Hi All:
 I just cross compile the arm-*-linux-uclibc cross tools for my board.
 The software I used are binutils 2.19 & gcc 4.3.2 & uClibc 0.9.30
 Everything seems ok but failed the last step while build the whole gcc compiler.
 The uClibc lib compiled successed. The configuration for arm is:"Generic Arm && Little endian", the lib generated and install in the right place.
 When I compile the gcc for the last time, the error occurs:"/toolchain/root/usr/lib/libc.so.0: could not read symbols: File in wrong format"

 I use 'file' command to see the format about the libc.so.o,it shows "lib/libuClibc-0.9.30.so: ELF 32-bit LSB shared object, ARM, version 1 (ARM), stripped".

  Also another thing is when I change directory to 'toolchain/root/usr/lib', using 'ls' conmmand to what file are, the error occurs "ls: error while loading shared libraries: libpthread.so.0: ELF file OS ABI invalid
"
  Can everyone give me a hand?

Mark
Comment 1 Khem Raj 2009-01-17 00:26:41 UTC 
this question is more appropriate for cross-compilation related mailing lists.
Comment 2 rhabarber1848 2009-02-19 21:41:04 UTC 
Maybe /toolchain/root/usr/lib/libc.so contains /lib/ as path instead of the complete path of your cross-compile environment.