/home/mitchell in prerelease tarball

[kelley.r.cook@gm.com]

Mark,

Sorry to bother you at such a late date, but I ran into an
issue with the GCC 3.1 prerelease tarball.

I was compiling GCC 3.1 under the i686-pc-mingw msys enviroment
which does not have bison nor yacc.

While compiling Java, it crashed with the following:

stage1/xgcc.exe -Bstage1/ -Bc:/mingw/i686-pc-mingw32/bin/ -c -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-DHAVE_CONFIG_H   -DCYGWIN_CROSS_DIR=\"c:/mingw/i686-pc-mingw32\" -I. -Ijava -I../../gcc-3.1-20020423/gcc -I../../gcc-3.1-20020423/gcc/java
-I../../gcc-3.1-20020423/gcc/config -I../../gcc-3.1-20020423/gcc/../include ../../gcc-3.1-20020423/gcc/java/boehm.c -o java/boehm.o
rm -f jc1.exe
stage1/xgcc.exe -Bstage1/ -Bc:/mingw/i686-pc-mingw32/bin/ -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H  -o jc1.exe \
        java/parse.o java/class.o java/decl.o java/expr.o java/constants.o java/lang.o java/typeck.o java/except.o java/verify.o java/zextract.o
java/jcf-io.o java/jcf-parse.o java/mangle.o java/mangle_name.o java/builtins.o java/jcf-write.o java/buffer.o java/check-init.o java/jcf-depend.o
java/jcf-path.o java/xref.o java/boehm.o mkdeps.o main.o libbackend.a -L../zlib -lz    ../libiberty/libiberty.a
java/parse.o: In function `read_import_dir':
/home/mitchell/gcc-3.1-20020423/gcc-3.1-20020423/gcc/java/parse.y:6872: undefined reference to `opendir'
/home/mitchell/gcc-3.1-20020423/gcc-3.1-20020423/gcc/java/parse.y:6880: undefined reference to `readdir'
/home/mitchell/gcc-3.1-20020423/gcc-3.1-20020423/gcc/java/parse.y:6891: undefined reference to `closedir'
^^^^^^^^^^^^^^
java/jcf-path.o: In function `jcf_path_extdirs_arg':
c:/tmp/build/gcc/../../gcc-3.1-20020423/gcc/java/jcf-path.c:371: undefined reference to `opendir'
c:/tmp/build/gcc/../../gcc-3.1-20020423/gcc/java/jcf-path.c:377: undefined reference to `readdir'
make[2]: *** [jc1.exe] Error 1
make[2]: Leaving directory `/c/tmp/build/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/c/tmp/build/gcc'
make: *** [restage2] Error 2

The error in this case was immaterial to this email, and was
easily corrected by tweaking mingw32.h to link in an
additional library file that was recently split off from the
main one.

My question is: should *your* computer's absolute pathname
be in the generated parse.c file that is in the tarball?

Kelley Cook

BTW, as an outsider, let me say that you are doing a
wonderful job as a release manager.  Especially compared to
the infighting that always seems to be involved in getting
the linux kernels released.