Hi Felix, thanks for the helpful responses. Just one note: On Sep 13, 2011, at 1:20 PM, Felix Fietkau wrote:
>> 1.) gcc/g++ binaries in toolchain >> >> OpenJDK uses the variable ALT_COMPILER_PATH to find the cross-compiler in >> short form (gcc/g++). But when using the compiler from >> $(TOOLCHAIN_DIR)/$(REAL_GNU_TARGET_NAME)/bin >> g++ fails, because a wrong relative path to cc1plus is used. As a >> workaround I copy the binaries to the parent directory and everything >> compiles fine: >> staging_dir/toolchain-i386_gcc-4.5-linaro_uClibc-0.9.32/i486-openwrt-linux-uclibc/bin$ >> cp * .. >> How to solve this in a smarter acceptable way? > How about creating something that matches the expected structure for OpenJDK > within its PKG_BUILD_DIR by using hard links or symlinks? > I'd like to avoid having package specific workarounds in the structure of the > toolchain dir. It wouldn't be a package specific workaround, because the compilers in this directory are unusable even to compile a hello world program: ./staging_dir/toolchain-i386_gcc-4.5-linaro_uClibc-0.9.32/i486-openwrt-linux-uclibc/bin/gcc -o hello hello.c gcc: error trying to exec 'cc1': execvp: No such file or directory It is kind of broken, isn't it? best regards Waldemar _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
