This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: gcj cross compile.. libgcj.so missing.
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether ln works... (cached) yes
checking whether ln -s works... (cached) yes
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gnatbind... no
checking whether compiler driver understands Ada... (cached) no
checking how to compare bootstrapped objects... (cached) cmp
--ignore-initial=16 $$f1 $$f2
checking for correct version of gmp.h... no
The following languages will be built: c,c++,java,objc
*** This configuration is not supported in the following subdirectories:
target-libada target-libgfortran
(Any other directories should still work fine.)
checking for bison... (cached) bison
checking for bison... (cached) bison -y
checking for gm4... (cached) m4
checking for flex... (cached) flex
checking for flex... (cached) flex
checking for makeinfo... (cached) makeinfo
checking for i686-pc-linux-gnu-ar... no
checking for ar... (cached) ar
checking for i686-pc-linux-gnu-as... no
checking for as... (cached) as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... (cached) dlltool
checking for i686-pc-linux-gnu-ld... no
checking for ld... (cached) ld
checking for i686-pc-linux-gnu-nm... no
checking for nm... (cached) nm
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... (cached) ranlib
checking for i686-pc-linux-gnu-windres... no
checking for windres... (cached) windres
checking for i686-pc-linux-gnu-objcopy... no
checking for objcopy... (cached) objcopy
checking for i686-pc-linux-gnu-objdump... no
checking for objdump... (cached) objdump
checking for i686-pc-linux-gnu-ar... (cached) arm-unknown-linux-gnu-ar
checking for i686-pc-linux-gnu-as... (cached) arm-unknown-linux-gnu-as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... (cached) dlltool
checking for i686-pc-linux-gnu-ld... (cached) arm-unknown-linux-gnu-ld
checking for i686-pc-linux-gnu-nm... (cached) arm-unknown-linux-gnu-nm
checking for i686-pc-linux-gnu-ranlib... (cached) arm-unknown-linux-gnu-ranlib
checking for i686-pc-linux-gnu-windres... no
checking for windres... (cached) windres
checking whether to enable maintainer-specific portions of Makefiles... no
checking if symbolic links between directories work... (cached) yes
creating ./config.status
creating Makefile
On 5/31/05, Andrew Haley <aph@redhat.com> wrote:
> Tom Rathbone writes:
> > Hi all,
> >
> > I just tried to compile a version (4.0.0) of gcc including gcj to
> > target arm-unknown-linux-gnu. I used crosstool to build the toolchain
> > and everything seemed to go well.. no errors. However when I try to
> > compile HelloWorld.java I get the error:
> >
> > # arm-unknown-linux-gnu-gcj HelloWorld.java -o HelloWorld
> > /home/tom/toolchain4/arm-unknown-linux-gnu/gcc-4.0-20050305-glibc-2.3.4/lib/gcc/arm-unknown-linux-gnu/4.0.0/../../../../arm-unknown-linux-gnu/bin/ld:
> > cannot find -lgcj
> > collect2: ld returned 1 exit status
> >
> > Looking in "gcc-4.0-20050305-glibc-2.3.4/arm-unknown-linux-gnu/lib/"
> > I see that I have no libgcj.so but i do have a libgcj.spec
> >
> > I also have gcc-4.0-20050305-glibc-2.3.4/share/java/libgcj-4.0.0.jar.
> >
> > Where should I be finding libgcj.so?
> >
> > If i look at the build directory I can see a directory called .libs/
> > (build-gcc/arm-unknown-linux-gnu/libjava/.libs) containing invalid
> > links called libgcj.so and libgcj.so.6 pointing to libgcj.so.6.0.0
> > which doesn't exist.. there is however a file called libgcj.so.6.0.0U
> >
> > If I update the links to point at this file and then compile with the
> > -L library path pointing at this directory then I get the following
> > error, I'm pretty sure this is totally the wrong but would like to
> > know where things have gone wrong.
> >
> > Does anybody have any ideas as to why I have no libgcj?
>
> Show us the output of the top-level gcc configure.
>
> Andrew.
>