public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/24403] --enable-java-awt=qt fails to build
Date: Tue, 17 Jul 2007 01:09:00 -0000	[thread overview]
Message-ID: <20070717010935.21327.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24403-5606@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from rob1weld at aol dot com  2007-07-17 01:09 -------
(In reply to comment #11)
> ping...
> > This is known and will not be fixed until 4.2.
> Now that 4.2 is released and it still doesn't work, can we get this working in
> 4.3?

Thats the spirit guys! So many threads have a reply that says: "it's broken,
don't do it" - I say enable it, and lets fix it!


I'm compiling "gcc version 4.3.0 20070716" and as far as "_building_" goes, it
works - not at the _testing_ part yet.

Make sure you alter file
"gcc-4_3-build/i686-pc-linux-gnu/libjava/classpath/native/jni/gtk-peer/Makefile"
to use "moc-qt4" and not "moc" (if your "moc" is for Qt3).


gcc/xgcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /root/downloads/gcc-4_3-trunk/configure --verbose
--enable-languages=c,ada,c++,fortran,java,objc,obj-c++ --prefix=/usr/test
--enable-objc-gc --disable-multilib
--with-gxx-include-dir=/usr/test/include/c++/4.3 --enable-libstdcxx-debug
--enable-static --enable-shared --enable-initfini-array --enable-__cxa_atexit
--enable-threads=posix --enable-version-specific-runtime-libs --enable-libssp
--enable-libmudflap --enable-libgomp --disable-werror --enable-nls
--with-included-gettext --enable-decimal-float --enable-debug
--enable-java-gc=boehm --with-x --x-includes=/usr/X11R6/include
--x-libraries=/usr/X11R6/lib --enable-java-awt=gtk,xlib,qt,x --enable-gtk-cairo
--enable-qt-peer --enable-xmlj --enable-gconf-peer --enable-libgcj-debug
--enable-plugin --enable-tool-wrappers --enable-portable-native-sync
--enable-examples --with-dwarf2 --with-stabs --enable-hash-synchronization
--enable-gc-debug --enable-interpreter --with-system-zlib --enable-libada
--with-tls --with-tune=athlon-xp --with-cpu=athlon-xp --with-arch=athlon-xp
--enable-stage1-checking=assert,df,fold,gc,misc,rtl,rtlflag,runtime,tree


-- 


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


  parent reply	other threads:[~2007-07-17  1:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-16 20:52 [Bug libgcj/24403] New: " bero at arklinux dot org
2005-10-16 20:54 ` [Bug libgcj/24403] " pinskia at gcc dot gnu dot org
2005-11-03  9:29 ` bero at arklinux dot org
2005-11-03 18:24 ` bero at arklinux dot org
2005-11-03 23:18 ` andreast at gcc dot gnu dot org
2005-11-08 20:06 ` tromey at gcc dot gnu dot org
2006-05-27 20:23 ` borisdusek at cmail dot cz
2006-07-03  0:08 ` pluto at agmk dot net
2006-08-09  1:04 ` bero at arklinux dot org
2006-08-15 16:16 ` bero at arklinux dot org
2006-08-17  1:09 ` bero at arklinux dot org
2007-05-24 10:53 ` bero at arklinux dot org
2007-05-24 16:59 ` tromey at gcc dot gnu dot org
2007-05-25 11:24 ` bero at arklinux dot org
2007-07-17  1:09 ` rob1weld at aol dot com [this message]
2007-07-17 13:05 ` rob1weld at aol dot com
2008-04-28 10:59 ` bero at arklinux dot org
2009-01-05 22:58 ` rob1weld at aol dot com
2009-01-19 17:43 ` rob1weld at aol dot com

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=20070717010935.21327.qmail@sourceware.org \
    --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).