Announcement

Collapse
No announcement yet.

Free COMPILERS and CROSS-COMPILERS for Linux and Windows.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    part 3 with --enable-libgcj, i.e.,

    Code:
    cd /gcc/gcc-win32-win32 
    /gcc/gcc-4.3.0/configure --build=i686-pc-linux-gnu \ 
                --target=i686-pc-mingw32 \ 
                --host=i686-pc-mingw32 \ 
                --enable-languages=c,c++,fortran,java,objc,obj-c++ \ 
                --enable-libgcj \
                --prefix=/mingw 
    make 
    make install
    compiles fine for gcc-4.3.0.

    Comment


    • #12
      Code:
      cd /gcc/gcc-linux-linux 
      /gcc/gcc-4.2.3/configure --enable-languages=c,c++,java
      make 
      make install
      Anyone know about the following error when compiling a native Java compiler on x86_64-unknown-linux-gnu with the above commands.

      Code:
      /usr/local/x86_64-unknown-linux-gnu/bin/ld: 
      ./libltdl/.libs/libltdlc.a(ltdl.o): 
      relocation R_X86_64_32S against `a local symbol' can not be used 
      when making a shared object; recompile with -fPIC
      ./libltdl/.libs/libltdlc.a(ltdl.o): could not read symbols: Bad value
      collect2: ld returned 1 exit status
      make[3]: *** [libgcj.la] Error 1
      make[3]: Leaving directory `/x/gcc-4.3.0/gcc-linux-linux/x86_64-unknown-linux-gnu/libjava'
      make[2]: *** [all-recursive] Error 1
      make[2]: Leaving directory `/x/gcc-4.3.0/gcc-linux-linux/x86_64-unknown-linux-gnu/libjava'
      make[1]: *** [all-target-libjava] Error 2
      make[1]: Leaving directory `/x/gcc-4.3.0/gcc-linux-linux'
      make: *** [all] Error 2
      It seems to be a libtool configuration error.
      Last edited by Jade; 05-12-2008, 10:05 AM.

      Comment


      • #13
        Originally posted by Jade View Post
        Anyone know about the following error when compiling a native Java compiler on x86_64-unknown-linux-gnu with the above commands.
        I don't think it's a libtool error, per se, but rather that something in the mix is trying to statically link a piece into a .so file.

        All pieces are really needing to be built as position independent code for an .so- it really ought to be complaining about it in 32-bit, but that'd be a bug in 32-bit mode for the toolchain if it didn't gripe about it.

        Comment


        • #14
          Originally posted by Svartalf View Post
          I don't think it's a libtool error, per se, but rather that something in the mix is trying to statically link a piece into a .so file.

          All pieces are really needing to be built as position independent code for an .so- it really ought to be complaining about it in 32-bit, but that'd be a bug in 32-bit mode for the toolchain if it didn't gripe about it.
          No. It is libtool for sure.

          Comment


          • #15
            I'm fairly sure it is a libtool configuration error and that it is in gcc-4.3.0/libjava/libltdl/configure (although some changes I made didn't work -- same error).

            The error only occurs when CONFIG_SHELL="/bin/sh -x" is set (compiles OK otherwise).

            Usually you want this so that you can track the errors.

            My guess is that some + or ++'s (from /bin/sh -x) are leaking into the process.

            Comment


            • #16
              I fixed about 12 instances where + and ++'s (from /bin/sh -x) are leaking into the process,.... but still get the same error. Oh well.

              Comment


              • #17
                The windows version of ADA does not compile under any version.

                Does anyone know about this?

                (Seems to be a library problem.)

                Comment


                • #18
                  Anyone know what Debian package contains the eclipse compiler (I need ecj1).

                  Comment


                  • #19
                    http://packages.debian.org/search?ke...ll&section=all

                    Comment


                    • #20
                      Thanks. Why do you think they only supply packages for alpha arm and armel?

                      Where is the support for i386 and x86_64?

                      Comment

                      Working...
                      X