Results 1 to 7 of 7
Even I'm facing this error .. Could anybody help ?...
- 04-02-2010 #1Just Joined!
- Join Date
- Apr 2010
- Posts
- 4
yyparse error
Even I'm facing this error .. Could anybody help ?
- 04-02-2010 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
yyparse is a function that is specific to your application which is created by yacc (or bison) using a parsing rule file. My guess is that you have either not configured the package correctly, or are not building it correctly. Since I haven't personally any experience with the SESC processor simulation environment, that is about as far as I can take you.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 04-02-2010 #3Just Joined!
- Join Date
- Apr 2010
- Posts
- 4
Hi Rubberman, Thanks for the promt reply
But now I'm facing new error while build-2-gcc
Its
ey/SESC/sescutils/src/gcc-3.4/gcc/gcc/. -I/home/mhatrey/SESC/sescutils/src/gcc-3.4/gcc/gcc/../include c-parse.c -o c-parse.o
gcc: c-parse.c: No such file or directory
gcc: no input files
make[1]: *** [c-parse.o] Error 1
make[1]: Leaving directory `/home/mhatrey/SESC/sescutils/build-mipseb-linux/obj/gcc-core-build/gcc'
make: *** [all-gcc] Error 2
Any suggestions ?
- 04-04-2010 #4Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Well, an expected file is missing, c-parse.c. Either it is in another subdirectory, or has not been created yet. Is there a configure script in the root directory of your build tree?
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 04-24-2010 #5Just Joined!
- Join Date
- Apr 2010
- Posts
- 4
There is build file which I guess configures the script..
#!/bin/sh
source ./build-common
GCC=gcc-3.4/gcc
GCC_CORE_BUILD_DIR=./obj/gcc-core-build
rm -rf $GCC_CORE_BUILD_DIR
mkdir -p $GCC_CORE_BUILD_DIR
cd $GCC_CORE_BUILD_DIR
export CZFLAGS="-fno-PIC -mno-abicalls"
$GNUSRC/$GCC/configure --target=${TARGET} --prefix=${PREFIX} \
--with-gnu-as --with-gnu-ld --disable-shared --disable-nls --disable-libmudflap\
--with-headers=$KERNHEADERS --enable-languages=c 2>&1 | tee ../gcc-core.conf.log
$MAKE all install 2>&1 | tee ../gcc-core.gmake.log
cd ../..
- 10-28-2010 #6Just Joined!
- Join Date
- Oct 2010
- Posts
- 1
- 10-28-2010 #7Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
This is an old thread. Please post your question to a new one. That said, please let us know which gcc compiler suite version you are trying to build. I have had no such problem building recent ones such as 4.5.1.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!


Reply With Quote
