public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/25026] -libXtst not detected [--enable-java-awt=gtk]
Date: Mon, 16 Oct 2006 20:10:00 -0000 [thread overview]
Message-ID: <20061016201052.4042.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25026-7667@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from pinskia at gcc dot gnu dot org 2006-10-16 20:10 -------
(In reply to comment #12)
> Be that as it may, there are plenty of cases where multilib is desired, just
> not for java. That should be an option.
Not really, if you don't have the libraries, you should not be building
multilib in general anyways.
Closing as invalid.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25026
next prev parent reply other threads:[~2006-10-16 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 20:44 [Bug libgcj/25026] New: " pluto at agmk dot net
2005-12-21 2:49 ` [Bug libgcj/25026] " smithj at rpath dot com
2005-12-21 2:51 ` smithj at rpath dot com
2006-02-21 20:30 ` smithj at rpath dot com
2006-10-16 15:40 ` pinskia at gcc dot gnu dot org
2006-10-16 15:53 ` dir at lanl dot gov
2006-10-16 16:53 ` smithj at rpath dot com
2006-10-16 18:53 ` dir at lanl dot gov
2006-10-16 18:55 ` smithj at rpath dot com
2006-10-16 19:00 ` tromey at gcc dot gnu dot org
2006-10-16 19:57 ` dir at lanl dot gov
2006-10-16 20:00 ` pinskia at gcc dot gnu dot org
2006-10-16 20:03 ` smithj at rpath dot com
2006-10-16 20:10 ` pinskia at gcc dot gnu dot org [this message]
2006-10-16 20:13 ` smithj at rpath dot com
2006-10-16 20:14 ` pinskia at gcc dot gnu dot org
2006-10-16 20:18 ` dir at lanl dot gov
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=20061016201052.4042.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).