# prev-gcc/xgcc -v
Using built-in specs.
Target: i386-pc-solaris2.11
Configured with: ../gcc_trunk/configure
--enable-languages=ada,c,c++,fortran,java,objc,obj-c++ --enable-shared
--disable-static --enable-decimal-float --with-long-double-128 --enable-nls
--with-included-gettext --enable-gather-detailed-mem-stats --with-stabs
--enable-debug -enable-largefile --enable-symvers --without-system-zlib
--enable-gtk-cairo --enable-qt-peer --enable-xmlj --enable-gconf-peer
--enable-gjdoc --enable-java-awt=gtk,xlib,qt,x --enable-gc-debug
--enable-libgcj-debug --enable-objc-gc --enable-libstdcxx-debug
--disable-stage1-checking --enable-checking=release --without-system-libunwind
--with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld
--with-ld=/usr/local/bin/ld
Thread model: posix
gcc version 4.4.0 20090111 (experimental) [trunk revision 143259] (GCC)
# gmake
...(many hours)
gmake[8]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/amd64/libffi'
gmake[7]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/amd64/libffi'
gmake[6]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/amd64/libffi'
gmake[5]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/libffi'
gmake[4]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/libffi'
gmake[3]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/libffi'
gmake[2]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/libffi'
Checking multilib configuration for zlib...
Checking multilib configuration for libjava...
mkdir -p -- i386-pc-solaris2.11/libjava
Configuring in i386-pc-solaris2.11/libjava
configure: creating cache ./config.cache
...
checking for gawk... (cached) gawk
checking for jar... jar
checking for zip... /usr/bin/zip
checking for unzip... /usr/bin/unzip
Illegal option: @
Usage: jar {ctxui}[vfm0Me] [jar-file] [manifest-file] [entry-point] [-C dir]
files ...
Options:
-c create new archive
-t list table of contents for archive
-x extract named (or all) files from archive
-u update existing archive
-v generate verbose output on standard output
-f specify archive file name
-m include manifest information from specified manifest file
-e specify application entry point for stand-alone application
bundled into an executable jar file
-0 store only; use no ZIP compression
-M do not create a manifest file for the entries
-i generate index information for the specified jar files
-C change to the specified directory and include the following file
If any file is a directory then it is processed recursively.
The manifest file name, the archive file name and the entry point name are
specified in the same order as the 'm', 'f' and 'e' flags.
Example 1: to archive two class files into an archive called classes.jar:
jar cvf classes.jar Foo.class Bar.class
Example 2: use an existing manifest file 'mymanifest' and archive all the
files in the foo/ directory into 'classes.jar':
jar cvfm classes.jar mymanifest -C foo/ .
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether to enable maintainer-specific portions of Makefiles... no
...
i386-pc-solaris2.11
checking if the linker (/usr/share/src/gcc_build/./gcc/collect-ld) is GNU ld...
yes
checking if the GNU linker (/usr/share/src/gcc_build/./gcc/collect-ld) supports
-Bsymbolic-functions... yes
checking dynamic linker characteristics... solaris2.11 ld.so
checking which variable specifies run-time library path... LD_LIBRARY_PATH
configure: error: Please supply an absolute path to the Escher library
When I look at the "trunk/libjava/configure" script I see this (Line 5524):
if test "$use_gtk_awt" != yes; then
ac_configure_args="$ac_configure_args --disable-gtk-peer --disable-plugin"
fi
if test "$use_qt_awt" != yes; then
ac_configure_args="$ac_configure_args --disable-qt-peer"
else
# We need this as qt is disabled by default in classpath.
ac_configure_args="$ac_configure_args --enable-qt-peer"
fi
if test "$use_x_awt" != yes; then
ac_configure_args="$ac_configure_args --without-escher"
else
# We need this as escher is disabled by default in classpath.
if test "$use_escher" != true; then
{ { echo "$as_me:$LINENO: error: Please supply an absolute path to the
Escher library" >&5
echo "$as_me: error: Please supply an absolute path to the Escher library"
>&2;}
# { (exit 1); exit 1; }; }
}
else
ac_configure_args="$ac_configure_args --with-escher=$with_escher"
fi
fi
if test "x$BUILD_GJDOC" = xno; then
ac_configure_args="$ac_configure_args --disable-gjdoc"
fi
Notice that if you do NOT use "--enable-java-awt=x" then you set
"--without-escher".
Notice that if you DO use "--enable-java-awt=x" then you set "--with-escher=".
I commented out the "{ (exit 1); exit 1; }; }" and replaced it with "}".
Now the configury can continue past this point. From what I recall of Escher
we can build awt-x without it and vice-versa.
Thanks,
Rob
PS: While someone is fixing that portion of the script could they please
clean-up the re-direction of the output of the check for: "checking for
unzip... /usr/bin/unzip".
--
Summary: [4.4 regression] Configure with "--enable-java-awt=x"
requires Escher
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: libgcj
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rob1weld at aol dot com
GCC build triplet: i386-pc-solaris2.11
GCC host triplet: i386-pc-solaris2.11
GCC target triplet: i386-pc-solaris2.11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38803
