Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: neutral (herse.apache.org: 212.159.14.214 is neither permitted
 nor denied by domain of mark.hindess@googlemail.com)
In-reply-to: <6e47b64f0704260839x368c11d2o402082be84dccd58@mail.gmail.com> 
References: <46306E6A.60204@gmail.com>
 <906dd82e0704260240m5eaef815g29b7113a6bf24892@mail.gmail.com>
 <46307B60.6080603@gmail.com>
 <6e47b64f0704260334y4c480f6akc33b2b4b5522a572@mail.gmail.com>
 <46308CF1.1020109@gmail.com>
 <6e47b64f0704260839x368c11d2o402082be84dccd58@mail.gmail.com>
Comments: In-reply-to "Stepan Mishura" <stepan.mishura@gmail.com>
   message dated "Thu, 26 Apr 2007 22:39:53 +0700."
From: Mark Hindess <mark.hindess@googlemail.com>
To: dev@harmony.apache.org
Subject: Re: [snapshot] Freezing the code for Milestone build? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 26 Apr 2007 21:33:12 +0100
Message-Id: <20070426203353.3042D10FB016@herse.apache.org>


On 26 April 2007 at 22:39, "Stepan Mishura" <stepan.mishura@gmail.com> wrote:
> On 4/26/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
> > Stepan Mishura wrote:
> > > On 4/26/07, Tim Ellison wrote:
> > >> Mikhail Loenko wrote:
> > >> > We should freeze when all CCs are in the up state [1]
> > >> >
> > >> > Can we use the snapshots [2]? My understanding is that the snapshots
> > >> > are updated in the "all CCs up" moments, so probably almost-a-week old
> > >> > snapshots are the best for the Milestone.
> > >>
> > >> Hey, I must have missed something!  Are they updated automatically by
> > >> somebody's build machine?
> > >
> > > I'd say they updated semi-automatically - I've not scheduled the
> > > script which builds and uploads them. And I kick the script when I see
> > > that all CC scenarios pass.
> >
> > I see.  Please would you also send mail to the list when you have
> > updated the snapshots so we all know they have changed.
> >
> 
> OK, I'm going to add 'release candidate' paragraph with links to
> milestone candidates.
> 
> > >> i.e. while we are testing them as candidates
> > >> are they likely to get overwritten?
> > >
> > > I think while we testing release candidates we should keep them on the
> > > site. So it makes sense for me to update the download page with
> > > separate links to release candidates.
> >
> > Agreed, and thanks for volunteering.
> > Can you do Linux candidates for both c++ library versions?
> >
> 
> Just to be sure that I do this in correct way. Currently I'm checking
> which libraries installed on machines I use for building. Some of them
> have libstdc++5 and some have both.
>
> What is correct way to check that a required library for building is
> used?

The easiest way is just to check the resulting .so files in
deploy/jdk/jre/bin with ldd.  I thought that the main issue was with the
icu libraries compiled against libstdc++5 that are in svn.

Earlier this week I checked in versions that use libstdc++.so.6 and
added an ant flag (-Duse.libstdc++6=true) to use them on the x86 builds.

Thinking about this some more though... we'll have a problem trying to
build with libstdc++.so.5 because although the libicu* files might use
libstdc++.so.5 your compiler might default to libstdc++.so.6 for the
awt native builds.  Mine certainly does and I don't know a quick way to
avoid this.

I'm afraid I'm going to be without web access until Monday so I can't be
more help.

-Mark.