mgardiner
2014-07-01 20:47:35 UTC
Hi,
Sorry if this is a duplicate message, but I had problems posting previously.
I'm a new OpenRISC user who just got the ORPSOCv3 tools working on my
Windows 7 machine recently. Now that my hardware development tools are
working I've been trying to get the OpenRISC toolchain setup through Cygwin
so I can start developing code.
I have been following the steps for building the GNU toolchain from source
on this page:
https://github.com/embecosm/chiphack/wiki/OpenRISC-tools-install
I ran into some minor issue with building GCC the first time, but after
running 'make' twice it completed without error. However, Cygwin always
gives me an error when I try to make newlib and gdb. I configure the build
with this command:
../or1k-src/configure --target=or1k-elf --prefix=/opt/or1k-toolchain
--enable-shared --disable-itcl --disable-tk --disable-tcl --disable-winsup
--disable-libgui --disable-rda --disable-sid --enable-sim --disable-or1ksim
--enable-gdb --with-sysroot --enable-newlib --enable-libgloss
--disable-werror
and then run 'make'. After a long time I get the following error when
building GDB:
checking compiler warning flags... -Wall -Wdeclaration-after-statement
-Wpointer-arith -Wpointer-sign -Wno-unused -Wunused-value -Wunused-function
-Wno-switch -Wno-char-subscripts -Wmissing-prototypes
-Wdeclaration-after-statement -Wempty-body -Wmissing-parameter-type
-Wold-style-declaration -Wold-style-definition -Wformat-nonliteral
checking for cygwin... yes
checking for ELF support in BFD... yes
checking for Mach-O support in BFD... no
checking for SOM support in BFD... no
checking whether to use lzma... auto
checking for liblzma... yes
checking how to link with liblzma... -llzma
checking for Tcl configuration... found /usr/lib/tclConfig.sh
checking for Tk configuration... found /usr/lib/tkConfig.sh
checking for existence of /usr/lib/tclConfig.sh... loading
checking for Tcl private headers... configure: error: could not find private
Tcl headers
Makefile:10206: recipe for target 'configure-gdb' failed
make[1]: *** [configure-gdb] Error 1
make[1]: Leaving directory
'/cygdrive/c/repos/softprocessors/openrisc/toolchain/bld-or1k-src'
Makefile:833: recipe for target 'all' failed
make: *** [all] Error 2
Can anyone point me to what this error might be? I don't understand why Tcl
is an issue here since I am using both --disable-tk and --disable-tcl when I
run the configure command.
If there isn't a good solution to this problem, can someone point me to the
most recent version of the GNU toolchain (bare metal) that is compatible
with Cygwin?
I have attached the config.log files from my bld-or1k-src folder and
bld-or1k-gcc folders if that will help with determining the issue.
config.log <http://openrisc.2316802.n4.nabble.com/file/n4641952/config.log>
(src)
config.log <http://openrisc.2316802.n4.nabble.com/file/n4641952/config.log>
(gcc)
Thanks.
--
View this message in context: http://openrisc.2316802.n4.nabble.com/Error-building-GNU-Toolchain-Bare-metal-with-Cygwin-tp4641952.html
Sent from the OpenRISC mailing list archive at Nabble.com.
Sorry if this is a duplicate message, but I had problems posting previously.
I'm a new OpenRISC user who just got the ORPSOCv3 tools working on my
Windows 7 machine recently. Now that my hardware development tools are
working I've been trying to get the OpenRISC toolchain setup through Cygwin
so I can start developing code.
I have been following the steps for building the GNU toolchain from source
on this page:
https://github.com/embecosm/chiphack/wiki/OpenRISC-tools-install
I ran into some minor issue with building GCC the first time, but after
running 'make' twice it completed without error. However, Cygwin always
gives me an error when I try to make newlib and gdb. I configure the build
with this command:
../or1k-src/configure --target=or1k-elf --prefix=/opt/or1k-toolchain
--enable-shared --disable-itcl --disable-tk --disable-tcl --disable-winsup
--disable-libgui --disable-rda --disable-sid --enable-sim --disable-or1ksim
--enable-gdb --with-sysroot --enable-newlib --enable-libgloss
--disable-werror
and then run 'make'. After a long time I get the following error when
building GDB:
checking compiler warning flags... -Wall -Wdeclaration-after-statement
-Wpointer-arith -Wpointer-sign -Wno-unused -Wunused-value -Wunused-function
-Wno-switch -Wno-char-subscripts -Wmissing-prototypes
-Wdeclaration-after-statement -Wempty-body -Wmissing-parameter-type
-Wold-style-declaration -Wold-style-definition -Wformat-nonliteral
checking for cygwin... yes
checking for ELF support in BFD... yes
checking for Mach-O support in BFD... no
checking for SOM support in BFD... no
checking whether to use lzma... auto
checking for liblzma... yes
checking how to link with liblzma... -llzma
checking for Tcl configuration... found /usr/lib/tclConfig.sh
checking for Tk configuration... found /usr/lib/tkConfig.sh
checking for existence of /usr/lib/tclConfig.sh... loading
checking for Tcl private headers... configure: error: could not find private
Tcl headers
Makefile:10206: recipe for target 'configure-gdb' failed
make[1]: *** [configure-gdb] Error 1
make[1]: Leaving directory
'/cygdrive/c/repos/softprocessors/openrisc/toolchain/bld-or1k-src'
Makefile:833: recipe for target 'all' failed
make: *** [all] Error 2
Can anyone point me to what this error might be? I don't understand why Tcl
is an issue here since I am using both --disable-tk and --disable-tcl when I
run the configure command.
If there isn't a good solution to this problem, can someone point me to the
most recent version of the GNU toolchain (bare metal) that is compatible
with Cygwin?
I have attached the config.log files from my bld-or1k-src folder and
bld-or1k-gcc folders if that will help with determining the issue.
config.log <http://openrisc.2316802.n4.nabble.com/file/n4641952/config.log>
(src)
config.log <http://openrisc.2316802.n4.nabble.com/file/n4641952/config.log>
(gcc)
Thanks.
--
View this message in context: http://openrisc.2316802.n4.nabble.com/Error-building-GNU-Toolchain-Bare-metal-with-Cygwin-tp4641952.html
Sent from the OpenRISC mailing list archive at Nabble.com.