From: Andrew Haley <aph@redhat.com>
To: Joshua Sumali <jsumali@redhat.com>
Cc: java-patches@gcc.gnu.org
Subject: Re: [patch] Create sdk style directory on install
Date: Mon, 30 Jun 2008 10:20:00 -0000 [thread overview]
Message-ID: <4868B351.10509@redhat.com> (raw)
In-Reply-To: <4863DD61.7020803@redhat.com>
Joshua Sumali wrote:
> Joshua Sumali wrote:
>> Andrew Haley wrote:
>>> Joshua Sumali wrote:
>>>
>>>
>>>> Please see the two (updated) patches. The updated patch for the
>>>> "Packager files" thread is now part of the sdk-home patch attached
>>>> here,
>>>> since I had to modify configure.ac to generate those packager files
>>>> this
>>>> time around.
>>>>
>>>> gcc-install-and-docs.patch creates man and info pages for aot-compile
>>>> and rebuild-gcj-db, and also documents the new install options
>>>> (--enable-java-home, --with-arch-directory, --with-python-dir) as
>>>> requested by Matthias.
>>>> gcc-libjava-sdk-home-update.patch is mostly the same as the first patch
>>>> I posted here, except with these main changes:
>>>>
>>>> - aot-compile and rebuild-gcj-db are now installed in $bindir
>>>> - if --with-python-dir is not specified (say, in a regular upstream
>>>> build) , classfile.py and aotcompile.py are installed in
>>>> $(prefix)/share/python. Otherwise, those Python modules will be
>>>> installed in the path specified with --with-python-dir. I modified
>>>> aot-compile -> aot-compile.in to append whichever path classfile.py and
>>>> aotcompile.py was installed in, so that it can actually find these
>>>> modules (it wouldn't look in $(prefix)/share/python by default).
>>>> - the SDK symlinked binaries, as well as aot-compile and
>>>> rebuild-gcj-db are now `transformed' as requested by Matthias.
>>>>
>>>
>>> OK, thanks.
>>>
>>>
>>>> Outstanding issues:
>>>> 1. @Matthias, I'm still not sure what you mean by "Same for using
>>>> GIJ_VERSION". Also, the issue about "why using the long version at
>>>> all?"
>>>> 2. rebuild-gcj-db doesn't have a licence header on the top of the
>>>> file... is this required? And if so, what's the right thing to do
>>>> about it?
>>>>
>>>
>>> Make it GPL.
>>>
>>> Andrew.
>>>
>> Updated rebuild-gcj-db with license header.
>>
>> Josh
> Hi,
>
> Updated documentation, and sdk patch attached. I think this one is ready
> to go in.
Nearly there.
Please don't put the ChangeLog files into the diffs. Post them as plain text.
Please assign all Red Hat copyrights to the FSF.
Do I take it that you don't have commit access to the gcc tree?
Andrew.
next prev parent reply other threads:[~2008-06-30 10:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 20:56 Joshua Sumali
2008-06-13 10:42 ` Andrew Haley
2008-06-13 12:42 ` Matthias Klose
2008-06-16 14:37 ` Joshua Sumali
2008-06-18 20:39 ` Joshua Sumali
2008-06-19 9:54 ` Andrew Haley
2008-06-19 14:24 ` Joshua Sumali
2008-06-20 4:13 ` Joshua Sumali
2008-06-26 18:18 ` Joshua Sumali
2008-06-30 10:20 ` Andrew Haley [this message]
2008-06-30 13:54 ` Joshua Sumali
2008-06-30 13:57 ` Andrew Haley
2008-06-30 14:39 ` Joshua Sumali
2008-07-01 13:59 ` Andrew Haley
2008-07-01 14:53 ` Joshua Sumali
2008-07-01 15:01 ` Andrew Haley
2008-07-02 13:07 ` Andrew Haley
2008-07-02 13:19 ` Joshua Sumali
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=4868B351.10509@redhat.com \
--to=aph@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=jsumali@redhat.com \
/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).