Home 
All forums OpenRISC or1ksim diff set autoconf automake aclocal upgrade, name change sim*-> or1ksim*, system wide .cfg file
All forums OpenRISC or1ksim diff set autoconf automake aclocal upgrade, name change sim*-> or1ksim*, system wide .cfg file 
1/1 
|
or1ksim diff set autoconf automake aclocal upgrade, name change sim*-> or1ksim*, system wide .cfg file
by Unknown on Mar 11, 2005 |
Not available! | ||
|
1 Upgrade autoconf automake autoheader files, (configure.diff is a big
file ) I'm not clear on the details but there is (was?) a good reason to generate configure with an old autoconf. Matjaz is the one who could fill you in on the delails.
2 Change the target binary from sim to or1ksim to avoid name collision
and to give the binary a more suitable name. After a make install the binary should be called or32-uclinux-sim (or something the like) if this isn't done then it should be fixed, but if everyone else is in agreement about a name change, let's change it.
3. sim.cfg was changed to or1ksim.cfg for the same reason as 2
I have issues with doing this. Only because in CVS moveing files a real pain. For starts you loose all its history (and becuase of my comment below it should not be needed).
4. or1ksim searches for or1ksim.cfg at current directory
${HOME}/.or1k/or1ksim.cfg and ${PREFIX}/etc directory. ${PREFIX}/etc directory was added to make or1ksim run with real default configuration file after installation and for system wide configuration . This is something that should not be done. sim.cfg is NOT a system wide configureation file. The file should probably be installed in something like $PREFIX/share/or1ksim and when the sim starts up and doesn't find a config file in the current directory (after checking the -f switch) it should issue a warning to the user on where to find the file. Also, the default configuration should be such that the sim is runnable (to a degree) without a config file availible.
5 target_cpu=or32 was changed to SIM_ARCH=or32 because of name collision
with autoconf system. I think that you're missunderstanding something here. target_cpu is used exactly because it _is_ an autoconf name. This is standard, ie. to build a simulator for dlx (instead of or32) you would give the --target=dlx parameter to configure. There is no reason (that I can see) to go with a non-standard configure switch when a standard one exists.
6 or32 is the default SIM_ARCH, so ./configure works without specifying
the SIM_ARCH=or32 there is also a need to remove cuc/Makefile from cvs sources. I have asked about this before, but the question went unanswered, so I dropped it... nog. |
|||
|
or1ksim diff set autoconf automake aclocal upgrade, name change sim*-> or1ksim*, system wide .cfg file
by Unknown on Mar 12, 2005 |
Not available! | ||
|
* György 'nog' Jeney (nog@sdf.lonestar.org) wrote:
> 1 Upgrade autoconf automake autoheader files, (configure.diff is a big
> file ) I'm not clear on the details but there is (was?) a good reason to generate configure with an old autoconf. Matjaz is the one who could fill you in on the delails. It's just that the autoconf tools on opencores server are really old, and upgrading them would be also a major pain...
> 2 Change the target binary from sim to or1ksim to avoid name collision
> and to give the binary a more suitable name. After a make install the binary should be called or32-uclinux-sim (or something the like) if this isn't done then it should be fixed, but if everyone else is in agreement about a name change, let's change it. I agree with Nog, let's call it or32-*-sim, '*' beeing something appropriate (like in gcc,...)
> 3. sim.cfg was changed to or1ksim.cfg for the same reason as 2
I have issues with doing this. Only because in CVS moveing files a real pain. For starts you loose all its history (and becuase of my comment below it should not be needed).
> 4. or1ksim searches for or1ksim.cfg at current directory
> ${HOME}/.or1k/or1ksim.cfg and ${PREFIX}/etc directory. ${PREFIX}/etc > directory was added to make or1ksim run with real default configuration > file after installation and for system wide configuration . This is something that should not be done. sim.cfg is NOT a system wide configureation file. The file should probably be installed in something like $PREFIX/share/or1ksim and when the sim starts up and doesn't find a config file in the current directory (after checking the -f switch) it should issue a warning to the user on where to find the file. Also, the default configuration should be such that the sim is runnable (to a degree) without a config file availible.
> 6 or32 is the default SIM_ARCH, so ./configure works without specifying
> the SIM_ARCH=or32 > > there is also a need to remove cuc/Makefile from cvs sources. I have asked about this before, but the question went unanswered, so I dropped it... Ok, if you insist ;), it's gone now. best regards, p. |
|||
1/1