If it's only GDB that needs or1ksim, then I could build Binutils, then
the GCC cross-compiler with Newlib, afterwards or1ksim and at the end
GDB. There would be no need to reconfigure or1ksim. Or have I missed
something?

Yes - that would work.

Please find attached a patch to prevent bld-all.sh from passing option --with-or1ksim to all configure scripts. That should reduce the confusion, as only GDB needs it.

Thanks,
   Ruben


Index: bld-all.sh
===================================================================
--- bld-all.sh  (Revision 783)
+++ bld-all.sh  (Arbeitskopie)
@@ -627,7 +627,7 @@
            ${top_srcdir}/configure --target=${target}                 \
                --with-pkgversion="${verstr}" --disable-shared         \
                --with-bugurl=http://bugzilla.opencores.org/           \
-               --with-or1ksim=${or1ksim_dir} --disable-werror         \
+               --disable-werror                                       \
                --enable-fast-install=N/A --disable-libssp             \
                --enable-languages=${langs} --prefix=${this_prefix} $*
 
@@ -862,7 +862,7 @@
        "${languages}" "${newlib_config}"
     # ??? should handle absolute pathnames.
     gnu_config ${config_flag} ${prefix} ${bd_elf_gdb} \
-       ../`dirname $0`/${gdb_dir} "${languages}"
+       ../`dirname $0`/${gdb_dir} "${languages}" 
"--with-or1ksim=${or1ksim_dir}"
 
     # Build all
     gnu_make ${build_flag} ${bd_elf} all-build all-binutils all-gas all-ld
@@ -974,7 +974,7 @@
     # only stage1 has been run previously).
     # ??? should handle absolute pathnames.
     gnu_config ${config_flag} ${prefix} ${bd_linux_gdb} \
-       ../`dirname $0`/${gdb_dir} "${languages}"
+       ../`dirname $0`/${gdb_dir} "${languages}" 
"--with-or1ksim=${or1ksim_dir}"
     gnu_make ${build_flag} ${bd_linux_gdb} all-build all-sim all-gdb
     gnu_make ${install_flag} ${bd_linux_gdb} install-sim install-gdb
 fi

_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc

Reply via email to