public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bero at arklinux dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/24403] --enable-java-awt=qt fails to build Date: Mon, 28 Apr 2008 11:00:00 -0000 [thread overview] Message-ID: <20080428105930.9352.qmail@sourceware.org> (raw) In-Reply-To: <bug-24403-5606@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from bero at arklinux dot org 2008-04-28 10:59 ------- ping... This missed 4.3 again, it should probably get in now before 4.4 enters freeze mode... Re the moc -> moc-qt4 change suggested in comment #14: This should be detected by the configure script, moc-qt4 is a nonstandard way some distributions use to tell moc 3.x apart from moc 4.x, other candidates for the correct moc include "moc4" and simply launching moc from a different path (/usr/lib/qt4/bin/moc) if the default moc is from 3.x -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24403
next prev parent reply other threads:[~2008-04-28 11:00 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:25 ` bero at arklinux dot org 2007-07-17 1:09 ` rob1weld at aol dot com 2007-07-17 13:06 ` rob1weld at aol dot com 2008-04-28 11:00 ` bero at arklinux dot org [this message] 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=20080428105930.9352.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).