public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/38298]  New: libjava link failures.
Date: Fri, 28 Nov 2008 02:21:00 -0000	[thread overview]
Message-ID: <bug-38298-7667@http.gcc.gnu.org/bugzilla/> (raw)

during building latest 4.4 snapshot i've got a linker error:

(...)
/bin/sh ./libtool --tag=GCJ --mode=link
/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/gcc/gcj
-B/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/x86_64-pld-linux/libjava/
-B/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/gcc/
-L/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/x86_64-pld-linux/libjava
-fomit-frame-pointer -O2 -march=x86-64  -Wl,--as-needed -Wl,-z,relro
-Wl,-z,combreloc  -o grmic --main=gnu.classpath.tools.rmic.Main -rpath
/usr/lib64/../lib64 -shared-libgcc   
-L/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/x86_64-pld-linux/libjava/.libs
libgcj-tools.la
libtool: link: /home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/gcc/gcj
-B/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/x86_64-pld-linux/libjava/
-B/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/gcc/
-fomit-frame-pointer -O2 -march=x86-64 -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z
-Wl,combreloc -o .libs/grmic --main=gnu.classpath.tools.rmic.Main
-shared-libgcc 
-L/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/x86_64-pld-linux/libjava/.libs
-L/home/users/pluto/rpm/BUILD/gcc-4.4-20081121/builddir/x86_64-pld-linux/libjava
./.libs/libgcj-tools.so -Wl,-rpath -Wl,/usr/lib64/../lib64
./.libs/libgcj-tools.so: undefined reference to `fmod'
collect2: ld returned 1 exit status
make[3]: *** [grmic] Error 1


-- 
           Summary: libjava link failures.
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pluto at agmk dot net
GCC target triplet: x86_64-gnu-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38298


             reply	other threads:[~2008-11-28  2:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28  2:21 pluto at agmk dot net [this message]
2008-12-24  1:37 ` [Bug libgcj/38298] " pinskia at gcc dot gnu dot org
2008-12-24  1:38 ` pinskia at gcc dot gnu dot org
2008-12-24 12:57 ` pluto at agmk dot net
2008-12-24 13:49 ` pinskia at gcc dot gnu dot org
2008-12-24 17:02 ` pluto at agmk dot net
2008-12-29  9:59 ` pluto at agmk dot net
2008-12-29 14:19 ` pinskia at gcc dot gnu dot org
2008-12-29 14:28 ` pluto at agmk dot net
2009-09-26  9:03 ` rwild at gcc dot gnu dot org
2009-09-27  6:49 ` rwild at gcc dot gnu dot org
2009-09-27  6:56 ` rwild at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-38298-7667@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).