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?
Thanks,
Stepan.
