1/1 
|
error in installing the GNU tool chain
by system2 on Oct 30, 2009 |
system2
Posts: 11 Joined: Oct 13, 2009 Last seen: Apr 20, 2010 |
||
|
Hello
I started the installation of the GNU tool chain on a windows machin and cygwin. I have refered to http://www.opencores.org/openrisc,gnu_toolchain. But in the end of insatallation i have an error message : or1ksim will open an xterm for console output as Linux is booting. ########################## or1ksim ############################### Insn MMU 0KB: 1 ways, 64 sets, entry size 1 bytes Data MMU 0KB: 1 ways, 64 sets, entry size 1 bytes Or1ksim 0.3.0 Building automata... done, num uncovered: 0/213. Parsing operands data... done. WARNING: Unable to open RX file stream. Cannot open Ethernet RX file "eth0.rx" Please if you have any idea about this error i will be greatful. |
|||
|
RE: error in installing the GNU tool chain
by jeremybennett on Oct 30, 2009 |
jeremybennett
Posts: 815 Joined: May 29, 2008 Last seen: Jun 13, 2019 |
||
|
Hello
I started the installation of the GNU tool chain on a windows machin and cygwin. I have refered to http://www.opencores.org/openrisc,gnu_toolchain. But in the end of insatallation i have an error message : or1ksim will open an xterm for console output as Linux is booting. ########################## or1ksim ############################### Insn MMU 0KB: 1 ways, 64 sets, entry size 1 bytes Data MMU 0KB: 1 ways, 64 sets, entry size 1 bytes Or1ksim 0.3.0 Building automata... done, num uncovered: 0/213. Parsing operands data... done. WARNING: Unable to open RX file stream. Cannot open Ethernet RX file "eth0.rx" Please if you have any idea about this error i will be greatful. Hi System2, Do you get the xterm starting correctly, and can you use Linux OK? These two warning messages are from the Or1ksim model for the PS2 (keyboard/mouse) and Ethernet interfaces. In the current Or1ksim these are modeled using files. So any input on the PS2 or Ethernet must be provided through files. The warnings are that no files can be found. This should not cause any problem to execution of the main model. HTH, Jeremy
-- |
|||
|
RE: error in installing the GNU tool chain
by julius on Oct 30, 2009 |
julius
Posts: 363 Joined: Jul 1, 2008 Last seen: May 17, 2021 |
||
|
But in the end of insatallation i have an error message
There's no error message there. It looks like it started up fine. Julius |
|||
|
RE: error in installing the GNU tool chain
by jt_eaton on Oct 30, 2009 |
jt_eaton
Posts: 142 Joined: Aug 18, 2008 Last seen: Sep 29, 2018 |
||
|
There's no error message there. It looks like it started up fine.
Julius ---------------------------------------------------- The problem is that when you run a script for the first time and you see messages like "Can't open file" then you have no idea if it is working or not. It does help if we can clean up issues like these by checking in dummy files into the database if that will prevent these warnings. It also really helps to print out a nice friendly "Program successful" in the log file. I'm surprised that opencores hasn't followed the norms used by softwares types in dealing with tool installs. Most packages that I have downloaded will have a README or INSTALL file that tells you to do 3 things: > ./configure > make all > su make install Configure is a program that checks your system to see if you have all the right tools and versions to build the package. If you need the gnu tool chain or bison or icarus then it checks your system and reports if something is missing. It is far better than simply putting this info in a doc file because a lot of people haven't a clue as to what is or is not in their distro. If configure passses then make all will compile,link and build the binary. make install will copy it to a bin directory that is in the PATH so it can be found. Should we encourage projects to create a ./configure file to report if they have all the tools they need? Should we include the MOF script in each project and have it called from a make file. John Eaton |
|||
|
RE: error in installing the GNU tool chain
by jeremybennett on Nov 2, 2009 |
jeremybennett
Posts: 815 Joined: May 29, 2008 Last seen: Jun 13, 2019 |
||
|
The problem is that when you run a script for the first time and you see messages like "Can't open file" then you have no idea if it is working or not. It does help if we can clean up issues like these by checking in dummy files into the database if that will prevent these warnings. It also really helps to print out a nice friendly "Program successful" in the log file.
Hi John, Fair comment. It reflects the fact that Or1ksim is only release 0.3.0, so still a long way from complete. The PS2 and Ethernet are still mostly stub entities. This should be logged in the bug tracker, so it gets picked up on a future release. The messages could indicate that the default behavior is still OK.
I'm surprised that opencores hasn't followed the norms used by softwares types in dealing with tool installs. Most packages that I have downloaded will have a README or INSTALL file that tells you
to do 3 things: > ./configure > make all > su make install Configure is a program that checks your system to see if you have all the right tools and versions to build the package. If you need the gnu tool chain or bison or icarus then it checks your system and reports if something is missing. It is far better than simply putting this info in a doc file because a lot of people haven't a clue as to what is or is not in their distro. If configure passses then make all will compile,link and build the binary. make install will copy it to a bin directory that is in the PATH so it can be found. But this is how the GNU tools and Or1ksim work. Or1ksim is built exactly this way. There is a known issue in the bug tracker that "make check" does not behave sensibly at present with Or1ksim. The Linux kernel and uClibc have their own variants on this (for configuration). The warnings aren't about something to do with building the tool. They are about the operational use of the tool. That's outside the realm of autoconf/automake. The one step not currently using autoconf/automake is the building of the Verilator and simulation models of the ORPSoC itself.
Should we encourage projects to create a ./configure file to report if they have all the tools they need? Should we include the MOF script in each project and have it called from a make file.
The MOF script sits above the individual tools. It's a convenience to download the source files and run the "configure; make; make install" for each tool in turn, the library and Linux kernel, then build the simulation model. It would be possible to rewrite this as a top level autoconf/automake script, but it's not clear that would represent an improvement or sensible use of effort. Even the GNU tool chain, with its unified development source tree, doesn't do this - you have to write a script to build each tool in turn. Jeremy
-- |
|||
1/1