no, I just change the CPU type to AMD Geode LX and system arch to Generic Embedded, else use the default.
At 2011-06-09 16:20:00，"René Rebe" <[email protected]> wrote: >Hi, > >On 09.06.2011, at 04:58, Jiangdn wrote: > >> hi, there >> >> I'm a newbie using t2 for the first time. I'm trying to compile a linux >> image on Ubuntu 10.04, but I get stucked at compiling linux26, I get the >> error message from the error-log as below: >> >> i686-t2-linux-gnu-nm: arch/x86/vdso/vdso32-int80.so.dbg: no symbols >> VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds >> i686-t2-linux-gnu-nm: arch/x86/vdso/vdso32-sysenter.so.dbg: no symbols >> CC kernel/spinlock.o >> OBJCOPY arch/x86/vdso/vdso32-int80.so >> OBJCOPY arch/x86/vdso/vdso32-sysenter.so >> VDSOSYM arch/x86/vdso/vdso32-syms.lds >> AS arch/x86/vdso/vdso32.o >> LD [M] fs/adfs/adfs.o >> LD fs/affs/built-in.o >> LD arch/x86/vdso/built-in.o >> CC [M] fs/affs/super.o >> arch/x86/vdso/vdso32-syms.lds: file not recognized: File truncated >> make[2]: *** [arch/x86/vdso/built-in.o] Error 1 >> make[1]: *** [arch/x86/vdso] Error 2 >> >> any solution? > > >Have not seen something like that, yet. Did you change some T2 config option? >E.g. the debug symbol separation? > > René >-- > René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin > http://exactcode.com | http://t2-project.org | http://rene.rebe.de >
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
