To better understand the parse error before "__THROW" in the 
helloworld.c I've done some other tries:
1) I installed from scratch all the needed packages in my suse 10.2
   following a topic that I've found on the acme forum 
  -> exactly same result and same errors. 

2) I've a new fox LX832, with kernel 2.6.15 so I compiled using the 
    option make cris-axis-linux-gnuuclibc before make. 
    But if I try to compile using make cris-axis-linux-gnu 
    (so for a fox running kernel 2.4.xx) and then make, it compiles
   perfectly both on the vmware debian and the suse installations

So it seems that the problem is related to the gnuuclib compilation 
mode, and I wonder if it is common to all the other fox (2.6.15) 
users. 

Please help 

ciao

franco








--- In [email protected], "proton_0305" <[EMAIL PROTECTED]> wrote:
>
> Hi Rolf,
> I've exactly the same problem. The strange is that I' using the 
> debian image that I got from the acme website ...
> Never the less, can you please explain in detail what you did, so I 
> can try the same solution ?
> thanks a lot for your help
> franco 
> 
> 
> 
> --- In [email protected], Rolf Schumacher <mailinglist@> 
> wrote:
> >
> > ok, I finaly made it.
> > There were problems with ncurses - it was not proberly installed.
> > 
> > Just to say there is nothing wrong with SDK.
> > 
> > Rolf
> > 
> > Rolf Schumacher wrote:
> > >
> > > Thank you for quick answering, John.
> > > Here is the ls -la info and a 'more .target-makefrag'
> > >
> > > [EMAIL PROTECTED]:/home/fox/devboard-R2_01/apps/helloworld$ ls -la
> > > total 24
> > > drwxr-xr-x 2 rsc rsc 4096 2007-06-30 22:03 .
> > > drwxr-xr-x 54 rsc rsc 4096 2007-06-30 08:19 ..
> > > -rw-r--r-- 1 rsc rsc 80 2007-06-30 08:23 helloworld.c
> > > -rw-r--r-- 1 rsc rsc 2344 2007-06-30 22:03 helloworld.out
> > > -rw-r--r-- 1 rsc rsc 206 2007-06-30 08:29 makefile
> > > -rw-r--r-- 1 rsc rsc 41 2007-06-30 08:36 .target-makefrag
> > > [EMAIL PROTECTED]:/home/fox/devboard-R2_01/apps/helloworld$ 
more .target-
> makefrag
> > > AXIS_BUILDTYPE=cris-axis-linux-gnuuclibc
> > > [EMAIL PROTECTED]:/home/fox/devboard-R2_01/apps/helloworld$
> > >
> > > John Crispin wrote:
> > > >
> > > > run ls -la in the folder of the hello world code and paste 
the 
> output
> > > > please
> > > >
> > > > Quoting schumacher_rolf <mailinglist@
> > > <mailto:mailinglist%40august.de>
> > > > <mailto:mailinglist%40august.de>>:
> > > >
> > > > > Instalation of SDK for FOX Board worked smooth on my Debian 
> linux.
> > > > > Also I'm able to compile and run helloworld using web 
> compilation.
> > > > >
> > > > > However, if compile it using the SDK I get lots of error 
> messages.
> > > > > What would be the next step to narrow a solution?
> > > > >
> > > > > Here are the first few error lines:
> > > > >
> > > > > In file included from
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stdio.h:42,
> > > > > from helloworld.c:1:
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stddef.h:201:
> > > > > syntax error before "typedef"
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stdio.h:44:25:
> > > > > bits/types.h: No such file or directory
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stdio.h:73:19:
> > > > > libio.h: No such file or directory
> > > > > In file included from helloworld.c:1:
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stdio.h:88:
> > > > > parse error before "fpos_t"
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stdio.h:137:28:
> > > > > bits/stdio_lim.h: No such file or directory
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stdio.h:150:
> > > > > parse error before "__THROW"
> > > > >
> > > >
> > > /usr/local/cris/lib/gcc-lib/cris-axis-linux-
> gnu/3.2.1/include/stdio.h:152:
> > > > > parse error before "__THROW"
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
>


Reply via email to