IcedTea 7 Patches for with-project=bsd - A Plan
mvfranz at gmail.com
Sun Mar 1 14:08:24 PST 2009
I have been able to compile IcedTea7 (changeset 1563 - January 28, 2009)
using a modified version of the bsd-port repo (changeset 58 - January 22,
2009) with zero. I have used Apple's 1.5 JDK and parts of gcc 4.3
java version "1.7.0_0-bsd"
IcedTea 1.9-pre-r70396cb4abf8 Runtime Environment (build 1.7.0_0-bsd-b44)
OpenJDK Core VM (build 14.0-b10, interpreted mode)
This is not a smooth process as I have some manual steps that I have not
been able to figure out.
What is the best way to integrate the necessary changes into IcedTea 7?
On Tue, Feb 3, 2009 at 9:27 PM, Michael Franz <mvfranz at gmail.com> wrote:
> Taking a different approach to getting IcedTea 7 to compile on OS X, I am
> trying to get the bsd repo to compile on Linux (Fedora 10). In
> investigating the patching problems closer, I wonder if this seems like a
> sound plan.
> 1. Identify the patches that break
> 2. move failing patches out of the main patch file into a project specific
> patch file
> 3. create equivalent patches for bsd
> 4. change the patch process to use base patches and then the project
> specific patches
> An example of this is icedtea-libraries.patch.
> There are 8 patches within this file that fail on the bsd repo. I would
> move these patches into icedtea-libraries-linux.patch (should this be jdk7?)
> and create bsd specific patches that are then put into
> The patch process can then apply the patches in icedtea-libraries.patch and
> then icedtea-libraries-<project>.patch.
> On a similar note, I have found that icedtea-libraries.patch and
> icedtea-linker-options.patch are patching the same line in
> - LDFLAGS += -z origin
> + LDFLAGS += -lz -z origin
> - LDFLAGS += -lz -z origin
> + LDFLAGS += -lz -Wl, -z -Wl,origin
> Is there a benefit to patching the same line twice (keeping logical changes
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the distro-pkg-dev