public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hanno Meyer-Thurow <h.mth@web.de>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] work on gcj for gentoo
Date: Sat, 25 Feb 2006 15:43:56 +0100	[thread overview]
Message-ID: <20060225154356.c399c5ed.h.mth@web.de> (raw)
In-Reply-To: <20060224182629.b5b50008.h.mth@web.de>

On Fri, 24 Feb 2006 18:26:29 +0100
Hanno Meyer-Thurow <h.mth@web.de> wrote:

> /bin/sh ./libtool --tag=GCJ --mode=link gcj --classpath=. -fassume-compiled -I./src -I. -I/usr/share/antlr/lib/antlr.jar -I. -g -O2  -Wl,-O1 -o gjdoc --main=gnu.classpath.tools.gjdoc.Main
> -Dgnu.gcj.runtime.VMClassLoader.library_control=never  -l-com-sun-javadoc -l-com-sun-tools-doclets-Taglet -l-gnu-classpath-tools-gjdoc antlr.so
> gcj --classpath=. -fassume-compiled -I./src -I. -I/usr/share/antlr/lib/antlr.jar -I. -g -O2 -Wl,-O1 -o .libs/gjdoc --main=gnu.classpath.tools.gjdoc.Main -Dgnu.gcj.runtime.VMClassLoader.library_control=never antlr.so  /var/tmp/portage/gjdoc-0.7.7/work/gjdoc-0.7.7/.libs/lib-com-sun-javadoc.so /var/tmp/portage/gjdoc-0.7.7/work/gjdoc-0.7.7/.libs/lib-com-sun-tools-doclets-Taglet.so /var/tmp/portage/gjdoc-0.7.7/work/gjdoc-0.7.7/.libs/lib-gnu-classpath-tools-gjdoc.so
> /var/tmp/portage/gjdoc-0.7.7/work/gjdoc-0.7.7/.libs/lib-gnu-classpath-tools-gjdoc.so: undefined reference to `java::lang::Class::getSuperclass()'
> collect2: ld returned 1 exit status
> make[2]: *** [gjdoc] Fehler 1

AFAIS it is fixed by this for x86/glibc usage, at least here:
(There is much more from toolchain.eclass that we want.)

...
    strip-flags

    ${S}/configure ${conf} \
        || die "configure failed!"

    make \
        BOOT_CFLAGS="${CFLAGS}" \
        LDFLAGS="-Wl,-O1" \
        LIBPATH="/opt/${PN}-${SLOT}/lib" \
        STAGE1_CFLAGS="-O" \
        profiledbootstrap \
        || die "make failed!"
...

---
Btw, I changed this to take effect now:

-	--with-languages=java
+	--enable-languages=c,c++,java

This stops objc to build.
We want language c for bootstrapping stuff.
Fixes that error?!

---
lib/libgcj.so.7.0.0 still links to libgcc_s.so.1 from system gcc.

I do not like to see that. But, however, the more we copy
from toolchain.eclass it may change.


Regards,
Hanno
-- 
gentoo-java@gentoo.org mailing list



  reply	other threads:[~2006-02-25 14:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 15:04 [gentoo-java] work on gcj for gentoo Hanno Meyer-Thurow
2006-02-21 15:42 ` Karl Trygve Kalleberg
2006-02-21 18:14   ` Hanno Meyer-Thurow
2006-02-21 18:21     ` Karl Trygve Kalleberg
2006-02-21 15:45 ` Joshua Nichols
2006-02-21 15:55   ` Joshua Nichols
2006-02-21 17:53   ` Hanno Meyer-Thurow
2006-02-22  8:16   ` Andrew Cowie
2006-02-27 22:38     ` Hanno Meyer-Thurow
2006-03-01 12:30       ` Andrew Cowie
2006-03-01 14:38         ` Hanno Meyer-Thurow
2006-02-28  7:34     ` [RESEND] " Hanno Meyer-Thurow
2006-02-22 16:51 ` Hanno Meyer-Thurow
2006-02-23  2:09 ` Andrew Cowie
2006-02-23 11:25   ` Hanno Meyer-Thurow
2006-02-24 17:26     ` Hanno Meyer-Thurow
2006-02-25 14:43       ` Hanno Meyer-Thurow [this message]
2006-02-28 10:25 ` Hanno Meyer-Thurow
2006-02-28 20:37   ` Hanno Meyer-Thurow
2006-03-02 10:35   ` Hanno Meyer-Thurow
2006-03-11 20:51 ` Hanno Meyer-Thurow
2006-03-12 18:25   ` Hanno Meyer-Thurow

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=20060225154356.c399c5ed.h.mth@web.de \
    --to=h.mth@web.de \
    --cc=gentoo-java@lists.gentoo.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