From: Matthias Klose <doko@ubuntu.com>
To: gnu_andrew@member.fsf.org
Cc: Andrew John Hughes <ahughes@redhat.com>,
GCC Java <java@gcc.gnu.org>,
debian-arm@lists.debian.org, debian-alpha@lists.debian.org,
distro-pkg-dev@openjdk.java.net
Subject: Re: icedtea6 build failures on alpha and armel using gcj
Date: Mon, 08 Mar 2010 12:41:00 -0000 [thread overview]
Message-ID: <4B94F065.60607@ubuntu.com> (raw)
In-Reply-To: <17c6771e1003080434r30405864v4e362752bc146ef3@mail.gmail.com>
On 08.03.2010 13:34, Andrew John Hughes wrote:
>> further, is it correct that the -ecj patch is applied to *both* the openjdk
>> and openjdk-ecj directory?
>>
>> $ ls -l build/openjdk*/jdk/src/share/classes/sun/misc/FloatConsts.java
>> -rw-rw-r-- 2 doko doko 4147 Feb 17 03:14
>> build/openjdk-ecj/jdk/src/share/classes/sun/misc/FloatConsts.java
>> -rw-rw-r-- 2 doko doko 4147 Feb 17 03:14
>> build/openjdk/jdk/src/share/classes/sun/misc/FloatConsts.java
>>
>> these are still hard links.
>
> No it's specifically only applied to -ecj patches.
Wrong. The patch is applied in the openjdk-ecj directory, but because all files
are hard links, it's applied in the openjdk directory as well. I don't see a way
to have patch break the hard links while patching.
> You should only
> ever ship a build created from the openjdk tree and not
> openjdk-ecj/boot (i.e. the second stage of a full build or the result
> of a --with-openjdk/--disable-bootstrap build), which has a number of
> features turned off (including Nimbus).
sure, this is always done in the Debian/Ubuntu builds. I didn't check this for
other distributions.
Matthias
next prev parent reply other threads:[~2010-03-08 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 16:49 Matthias Klose
2010-03-01 19:54 ` Andrew John Hughes
2010-03-08 11:46 ` Matthias Klose
2010-03-08 12:35 ` Andrew John Hughes
2010-03-08 12:41 ` Matthias Klose [this message]
2010-03-08 12:45 ` Andrew John Hughes
2010-03-08 14:36 ` Lennart Sorensen
2010-03-08 15:17 ` 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=4B94F065.60607@ubuntu.com \
--to=doko@ubuntu.com \
--cc=ahughes@redhat.com \
--cc=debian-alpha@lists.debian.org \
--cc=debian-arm@lists.debian.org \
--cc=distro-pkg-dev@openjdk.java.net \
--cc=gnu_andrew@member.fsf.org \
--cc=java@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).