porting icedtea6 to FreeBSD

[Jason Helfman]

On Tue, Apr 17, 2012 at 7:56 AM, Andrew Hughes <ahughes at redhat.com> wrote:

> ----- Original Message -----
> >
> >
> >
> > On Tue, Apr 17, 2012 at 4:51 AM, Andrew Hughes < ahughes at redhat.com >
> > wrote:
> >
> >
> >
> > ----- Original Message -----
> > > On Mon, Apr 16, 2012 at 09:59:00AM -0400, Andrew Hughes thus spake:
> > > >> Any thoughts on any of this?
> > > >> Thanks, again.
> > > >>
> > > >> -jgh
> > > >
> > > >What are you doing here?
> > > >
> > > >/usr/bin/sed -i.bak -e 's|--dry-run||g'
> > >
> >/usr/local/workspace/redports/java/icedtea6/work/icedtea6-1.11.1/Makefile.am
> > >
> >/usr/local/workspace/redports/java/icedtea6/work/icedtea6-1.11.1/Makefile.in
> > > >/usr/bin/sed -i.bak -e 's|--check|-q|g'
> > >
> >/usr/local/workspace/redports/java/icedtea6/work/icedtea6-1.11.1/Makefile.am
> > >
> >/usr/local/workspace/redports/java/icedtea6/work/icedtea6-1.11.1/Makefile.in
> > > >
> > > >If you're removing --dry-run, you're going to be applying the
> > > >patch
> > > >twice, which is why it's failing.
> > > >--
> > > >Andrew :)
> > >
> > > I've modified this to test the patch which in FreeBSD is the "-C"
> > > switch,
> > > and the "-q" is for SHASUM's to only output the hash.
> > >
> > > I was able to get much further in the build! Any thoughts on why
> > > this
> > > patch
> > > was seen as already applied?
> > >
> >
> > Because the build tests the patch, then applies it if that passes. If
> > you
> > removed --dry-run from the first invocation and didn't replace it
> > with -C,
> > you'd be applying the patch twice instead.
> >
> >
> >
> > That is what I have done, though. --dry-run is being replaced with -C
> > in the build.
> > Is something else showing up?
> >
> > -jgh
> >
> >
>
> And it's still failing in the same way?  I thought you said you'd got much
> further... :-S
> --
> Andrew :)
>

Yes, it is failing in the same way but much further into the build.
Initially, it would fail at the first/second patch.
I attached the latest buildlog to my email last night. It should show the
issue, and with what patch the problem
was with.

-jgh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20120417/29705f49/attachment.html