On Fri, Mar 19, 2010 at 07:43:26AM +0800, William Kenworthy wrote:
> The failure message should list a log file containing more detail on
> whats failed. Often (actually usually!) its a bug the devs might not be
> aware of as they usually build from within their own environment and not
> from a complete build the whole distro from scratch.
>
> With the info from the log file, if its not an obvious fix, pastebin it
> and ask on irc (#openmoko-cdeve)
>
> BillK
This from attachement is almost enough
libtool: relink: ccache arm-oe-linux-gnueabi-gcc -march=armv4t -mtune=arm920t
-mthumb-interwork -mthumb -shared .libs/tif_aux.o .libs/tif_close.o
.libs/tif_codec.o .libs/tif_color.o .libs/tif_compress.o .libs/tif_dir.o
.libs/tif_dirinfo.o .libs/tif_dirread.o
.libs/tif_dirwrite.o .libs/tif_dumpmode.o .libs/tif_error.o
.libs/tif_extension.o .libs/tif_fax3.o .libs/tif_fax3sm.o .libs/tif_flush.o
.libs/tif_getimage.o .libs/tif_jbig.o .libs/tif_jpeg.o .libs/tif_jpeg_12.o
.libs/tif_luv.o .libs/tif_lzw.o .libs/tif_next.o
.libs/tif_ojpeg.o .libs/tif_open.o .libs/tif_packbits.o .libs/tif_pixarlog.o
.libs/tif_predict.o .libs/tif_print.o .libs/tif_read.o .libs/tif_strip.o
.libs/tif_swab.o .libs/tif_thunder.o .libs/tif_tile.o .libs/tif_unix.o
.libs/tif_version.o .libs/tif_warning.o
.libs/tif_write.o .libs/tif_zip.o -Wl,--whole-archive ../port/.libs/libport.a
-Wl,--no-whole-archive
-L/home/jussi/build-shr/shr-unstable/tmp/staging/armv4t-oe-linux-gnueabi/usr/lib
-L/home/jussi/build-shr/shr-unstable/tmp/work/armv4t-oe-li
nux-gnueabi/tiff-3.9.2+4.0.0beta5-r1/image/usr/lib -L/usr/lib -ljpeg -lz -lm
-lc -march=armv4t -mtune=arm920t -mthumb-interwork -mthumb -Wl,-rpath-link
-Wl,/home/jussi/build-shr/shr-unstable/tmp/staging/armv4t-oe-linux-gnueabi/usr/lib
-Wl,-O1 -Wl,--hash-style=gnu
-Wl,-soname -Wl,libtiff.so.5 -o .libs/libtiff.so.5.0.2
You shouldn't see -L/usr/lib
-L/home/jussi/build-shr/shr-unstable/tmp/staging/armv4t-oe-linux-gnueabi/usr/lib
or
-L/home/jussi/build-shr/shr-unstable/tmp/cross/armv4t/arm-oe-linux-gnueabi/lib/
is much better
/usr/lib/libgcc_s.so: file not recognized: File format not recognized
is because it tries to use libgcc_s.so from your computer instead armv4t staged
in OE
Please check log.do_configure and config.log and also created .la, why it finds
/usr/lib/libgcc_s.so
instead
cross/armv4t/arm-oe-linux-gnueabi/lib/libgcc_s.so
or even
staging/armv4t-oe-linux-gnueabi/usr/lib/gcc/arm-oe-linux-gnueabi/4.4.3/libgcc_s.so
Maybe it fould find
staging/armv4t-oe-linux-gnueabi/usr/lib/gcc/arm-oe-linux-gnueabi/4.4.3/libgcc_s.so
if you build gcc first.
Regards,
--
uin:136542059 jid:[email protected]
Jansa Martin sip:[email protected]
JaMa
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
