gcc was configured with: --target=$TARGET --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=$PREFIX --with-cpu=ep9312 --with-fpu=maverick --enable-cxx-flags=-mcirrus-fix-invalid-insns --disable-altivec --disable-nls --disable-checking --disable-werror --disable-libunwind-exceptions --disable-multilib --disable-libgcj --enable-languages=c --disable-shared --disable-threads --without-headers --disable-libmudflap --disable-__cxa_atexit --enable-target-optspace --enable-clocale=uclibc
There are unresolved symbols in libgcc, such as, for example, __divdf3. This causes uclibc compilation to fail. The problem doesn't exist when I compile gcc without specifying the --with-cpu=ep9312 and --with-fpu=maverick options. It seems that gcc does not define FLOAT or TFLOAT for the maverick architecture. Could this be the problem? -- Summary: problems caused by unresolved symbols in libgcc Product: gcc Version: 4.0.2 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: nekkar at libero dot it GCC build triplet: x86_64-pc-linux-gnu GCC host triplet: x86_64-pc-linux-gnu GCC target triplet: armv4l-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25044