This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: /home/mitchell in prerelease tarball
- From: Tom Tromey <tromey at redhat dot com>
- To: kelley dot r dot cook at gm dot com
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: 07 May 2002 14:33:40 -0600
- Subject: Re: /home/mitchell in prerelease tarball
- References: <OF112E6C01.6750123F-ON85256BB2.0063A062@mail.gm.com>
- Reply-to: tromey at redhat dot com
>>>>> "Kelley" == kelley r cook <kelley.r.cook@gm.com> writes:
Kelley> I was compiling GCC 3.1 under the i686-pc-mingw msys enviroment
Kelley> which does not have bison nor yacc.
Kelley> While compiling Java, it crashed with the following:
As far as I know, native mingw builds of gcj, and especially libgcj,
aren't supported. There are still problems making this work.
Kelley> c:/tmp/build/gcc/../../gcc-3.1-20020423/gcc/java/jcf-path.c:371: undefined reference to `opendir'
Kelley> My question is: should *your* computer's absolute pathname
Kelley> be in the generated parse.c file that is in the tarball?
This is a side effect of how the parse.c file is currently generated.
There are other ways to build this file, but last year I changed
java/Make-lang.in to use this method to make debugging gcj a little
more friendly:
http://gcc.gnu.org/ml/gcc-patches/2001-03/msg01579.html
Tom