On 26 April 2007 at 22:39, "Stepan Mishura" <[EMAIL PROTECTED]> wrote: > On 4/26/07, Tim Ellison <[EMAIL PROTECTED]> 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.
