I patched the architecture/arm/archtest.sh in order to fix the toolchain name when using uclibc.
I started again my build. This time, the toolchain name was arm-t2-linux-uclibcgnueabi and ncurses built successfully. I already encountered the same sort of problems when trying to build a powerpc tool chain that supports the SPE of the e500 core. Without the correct toolchain name, lots of troubles. Le samedi 22 août 2009 à 19:00 +0200, Thomas Jourdan a écrit : > Hi > > I tried to cross build an embedded minimal target for my beagle board, > with uclibc. It fails when building ncurses : > > == 18:42:37 =[1]=> Building base/ncurses [5.7 8.0-trunk]. > -> Parallel build using 4 jobs enabled. > -> Reading package config: package/base/ncurses/ncurses.conf > -> Preparing build in > src.ncurses.cortexa8-embedded.20090822.184236.25682.desktop > -> Building. Writing output to $root/var/adm/logs/1-ncurses.out > !> ../obj_s/tclock.o: In function `main': > !> tclock.c:(.text+0x3ac): undefined reference to `sincos' > !> tclock.c:(.text+0x5c0): undefined reference to `sincos' > !> tclock.c:(.text+0x5f4): undefined reference to `sincos' > !> tclock.c:(.text+0x670): undefined reference to `sincos' > !> collect2: ld returned 1 exit status > !> Due to previous errors, no 1-ncurses.log file! > !> (Try enabling xtrace in the config to track an error inside the build > system.) > -> $root/var/adm/logs/1-ncurses.out -> 1-ncurses.err > == 08/22/09 18:43:31 =[1]=> Aborted building package ncurses. > > I found a thread : > http://www.mail-archive.com/[email protected]/msg257036.html > where they explain the issue might come from the toolchain triplet. > > I checked and T2 generates arm-t2-linux-gnueabi toolchain for arm / > eabi / uclibc configuration. Shouldn't it be > arm-t2-linux-uclibcgnueabi ? > > Regards, > Thomas > > > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [email protected] with a subject of: unsubscribe t2 >
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
