From: Dr Andrew John Hughes <gnu_andrew@member.fsf.org>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Matthias Klose <doko@ubuntu.com>,
Dr Andrew John Hughes <gnu_andrew@member.fsf.org>,
Java Patch List <java-patches@gcc.gnu.org>
Subject: Re: Classpath Merge (1/3): libgcj-import-20100921
Date: Tue, 05 Oct 2010 23:45:00 -0000 [thread overview]
Message-ID: <AANLkTikg_Ex8nYd5isEaWS=hmNGo86K+Z7ZZfjcugaMc@mail.gmail.com> (raw)
In-Reply-To: <20101005180430.GH30152@gmx.de>
On 5 October 2010 19:04, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> Hello,
>
> * Matthias Klose wrote on Tue, Oct 05, 2010 at 10:43:55AM CEST:
>> On 28.09.2010 23:23, Dr Andrew John Hughes wrote:
>> >Attached is a merge of GNU Classpath into trunk from the tag
>> >libgcj-import-20100921. This tag was created against revisions as of
>> >2010-06-01 to avoid the whitespace changes on the 3rd. My intention
>> >is to post separate whitespace fixes for gcj and then a second merge
>> >containing changes after this change to Classpath. This merge however
>> >contains most of the changes that have lingered in Classpath for a
>> >long time since the merge for 4.4.
>> >
>> >This took longer than expected, mainly due to the presence of
>> >generated autotools files in the gcj tree which require regeneration
>> >with specific versions. gcj seems to have decided to use libtool
>> >2.2.7a, which doesn't exist as a release on
>> >http://ftp.gnu.org/gnu/libtool/ and I ran into conflicts with macros
>> >from the GNU Classpath import which used the system 2.2.10 install.
>> >In the end, the solution was to remove the Classpath copy from the m4
>> >directory, which caused the 2.2.7a macros in
>> >the top-level config directory to be used.
>>
>> CCing Ralf for the auto*/libtool stuff. Maybe it's worth documenting the
>> missing libtool bits/versions in libjava/HACKING?
>
> FWIW, I intend to update Libtool bits in GCC to 2.4 before 4.6, not the
> least in order to get LTO working throughout the tree.
>
> Inside GCC, it is important that you pick up toplevel and
> toplevel/config directories for aclocal (ACLOCAL_AMFLAGS = -I .. -I
> ../config) so that override.m4 is found.
>
> configure.ac:
>> +if ...
>> +...
>> +else
>> + AM_CONDITIONAL(GCJ_JAVAC, no)
>> fi
>
> Having an AM_CONDITIONAL in a shell conditional leads to trouble.
> Instead, use the shell condition inside an AM_CONDITIONAL at outer
> level:
>
> AM_CONDITIONAL([GCJ_JAVAC], [test "$foo" = bar])
>
> Cheers,
> Ralf
>
We already do that in libjava/classpath/m4/ac_prog_javac.m4:
AM_CONDITIONAL(GCJ_JAVAC, test x"${JAVAC_IS_GCJ}" = xyes)
The addition above is necessary because we can't compute JAVAC_IS_GCJ
if java maintainer mode is turned off as there is no javac.
It's not ideal, I agree. I'll see if I can find a better solution.
--
Andrew :-)
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
next prev parent reply other threads:[~2010-10-05 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 21:23 Dr Andrew John Hughes
2010-10-05 8:44 ` Matthias Klose
2010-10-05 13:01 ` Dr Andrew John Hughes
2010-10-05 18:04 ` Ralf Wildenhues
2010-10-05 23:45 ` Dr Andrew John Hughes [this message]
2010-10-07 12:26 ` Andrew Haley
2010-10-12 17:26 ` Dr Andrew John Hughes
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='AANLkTikg_Ex8nYd5isEaWS=hmNGo86K+Z7ZZfjcugaMc@mail.gmail.com' \
--to=gnu_andrew@member.fsf.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=doko@ubuntu.com \
--cc=java-patches@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).