public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "brian at dessent dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/38438] build error in x86_64-unknown-linux-gnu/32/libjava
Date: Mon, 08 Dec 2008 00:30:00 -0000 [thread overview]
Message-ID: <20081208003034.16430.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38438-3511@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from brian at dessent dot net 2008-12-08 00:30 -------
Subject: Re: build error in
x86_64-unknown-linux-gnu/32/libjava
> I have the sources in ~/tmp/gcc, and I build in ~/tmp/gcc/build using
> ../configure.
Oh, that's definitely not good. To quote
<http://gcc.gnu.org/install/configure.html>, "building where objdir is a
subdirectory of srcdir is unsupported." Start over with a clean tree
and separate build dir.
> I am using automake 1.10.2, libtool 2.2.6, autoconf 2.63, make 3.81 and
> binutils 2.19 in case any of that matters.
As long as you update from SVN properly (using contrib/update_gcc so
that timestamps are updated) then the autoconf/automake/libtool on your
system should never run unless you modify an *.am/*.ac/*.m4 source
file. (And if you do do that, then you have to use the specific
project-blessed versions to regenerate anyway, namely 2.59/1.9.6.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38438
prev parent reply other threads:[~2008-12-08 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 21:01 [Bug libgcj/38438] New: " felix-gcc at fefe dot de
2008-12-07 21:46 ` [Bug libgcj/38438] " felix-gcc at fefe dot de
2008-12-07 22:48 ` brian at dessent dot net
2008-12-07 23:38 ` felix-gcc at fefe dot de
2008-12-08 0:17 ` felix-gcc at fefe dot de
2008-12-08 0:30 ` brian at dessent dot net [this message]
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=20081208003034.16430.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).