Re: [openrisc] Build problems with or1ksim

[Richard Prescott <rip@step.polymtl.ca>]

Ok I understood what happen.

I updated configure.in where I did the mistake then I checked in configure
and configure.in

I fix up the mistake and checked in configure.in (not configure).  Those
who updated their cvs didn't had any trouble because configure.in was
newer than configure so configure got updated by make.

I checked in configure now, redo a checkout and everything should be fine.

Sorry

Richard

On Tue, 5 Nov 2002, Karen Locke wrote:

> Hi,
> I've just managed to build version 1.96 of or1ksim (cvs checkout about four
> hours ago).  I did have a problem with it finding include files in
> or1ksim/peripheral/channels, because the makefile lists the relevant include
> directory as or1ksim/peripheral\channels (note backslash).  Building on my
> linux system, the path wasn't interpreted correctly.  I patched around it by
> editing the Makefile.
>
> I'm quite new to the automake/autoconf method of creating makefiles, so I
> don't quite know which file to edit to fix the problem correctly.
> Alternatively, is there some setting I can use to make path parsing not care
> about slashes vs. backslashes?
>
> I also had a problem that it couldn't find a file called "depcomp" in the top
> level directory when I intially configured with the following command:
> ./configure --target=or32 --prefix=/home/sdk/or32.
>
> The problem went away when I added --disable-dependency-tracking.  Is there
> anything i should worry about if I don't use dependency tracking?
>
> Thanks,
> K
>
>
> Karen Locke
> Silicon Magic Corporation
> karenl@simagic.com
> --
> To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml
>

--------------------------------------------------------------
"Coffee should be black as hell, strong as death, and sweet as love."
				-Turkish Proverb

--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml