Re: Build problems with CVS under Solaris 8/SPARC

[Albert Chin-A-Young <china at thewrittenword dot com>]

On Fri, Oct 13, 2000 at 05:14:39PM -0400, Kaveh R. Ghazi wrote:
>  > From: Albert Chin-A-Young <china@thewrittenword.com>
>  > 
>  > gmake[2]: Entering directory `/opt/build/gcc-2.97/objdir/gcc'
>  > cd cp && gmake ../../../gcc/cp/parse.c
>  > gmake[3]: Entering directory `/opt/build/gcc-2.97/objdir/gcc/cp'
>  > expect 33 shift/reduce conflicts and 58 reduce/reduce conflicts.
>  > cd ../../../gcc/cp; bison  -d -o p$$.c parse.y ; \
>  > grep '^#define[         ]*YYEMPTY' p$$.c >> p$$.h ; \
>  > mv -f p$$.c ../../../gcc/cp/parse.c ; mv -f p$$.h ../../../gcc/cp/parse.h
>  > parse.y contains 35 shift/reduce conflicts and 58 reduce/reduce conflicts.
>  > mv: cannot rename p24233.c: No such file or directory
>  > mv: cannot rename p24233.h: No such file or directory
>  > gmake[3]: *** [../../../gcc/cp/parse.c] Error 2
>  > 
>  > It looks like there is one extra '..'. When this command is run, the
>  > currect directory is '/opt/build/gcc-2.97/gcc/cp'. And, $(PARSE_C) is
>  > ../../../gcc/cp/parse.c. So, the mv is going to fail. So, a patch
>  > below generates the p$$.[ch] files in a subshell then uses $(srcdir)
>  > to specify the original location of the p$$.[ch] files for the mv.
> 
> Sorry, this was caused by a recent patch of mine.  I'll fix it.
> 
> Just so I understand things, are you building gcc within its srcdir or
> do you have separate src and build directories?
> 
> I.e. how do you call configure?  Is it ./configure or ../foo/configure
> or /foo/bar/baz/configure or something else?

I run ../configure.

-- 
albert chin (china@thewrittenword.com)