Re: Heads-up - manual toolchain update required soon

[Henry Robinson]

Ok, this is done, and the patch is committed to master. As a reminder,
you'll need to remove the cached glog library in your toolchain, as per
below.

IMPALA-5174: Bump gflags to 2.2.0-p1

This gflags patch adds DEFINE_int32_hidden() etc. macros, which suppress
flags from appearing in /varz, --help and other flag enumerations.

Our toolchain glog is statically linked against gflags, and therefore
had to be rebuilt, however its version number did not change. You will
likely need to do the following:

rm -rf ${IMPALA_TOOLCHAIN}/glog-0.3.4-p2/

before running bin/bootstrap_toolchain.py, otherwise building Impala may
fail with a linking error.


On 15 May 2017 at 11:09, Henry Robinson  wrote:

> Let's do it individually. I'll push an update patch for my change now.
>
> On 14 May 2017 at 06:09, Lars Volker  wrote:
>
>> I recently bumped the Breakpad version in the toolchain repo and now would
>> like to pull that into master. The change to do so is here:
>> https://gerrit.cloudera.org/#/c/6883/
>>
>> Should I wait until gflags has been pulled into master and rebase? Or
>> would
>> you like me to bump gflags in my change, too?
>>
>> On Tue, May 9, 2017 at 12:21 AM, Henry Robinson  wrote:
>>
>> > I'm about to start the process of getting IMPALA-5174 committed to the
>> > toolchain. This patch changes gflags to allow 'hidden' flags that won't
>> > show up on /varz etc.
>> >
>> > The toolchain glog has a dependency on gflags, meaning that the
>> installed
>> > glog library needs to be built against the installed gflag library. So
>> when
>> > the new gflag gets pulled in, you will need the new glog as well.
>> >
>> > However, the toolchain scripts won't detect that anything has changed
>> for
>> > glog, because there's no version number change (changing the toolchain
>> > build ID doesn't cause the toolchain scripts to invalidate
>> dependencies).
>> >
>> > Rather than introduce a spurious version bump with an empty patch file
>> or
>> > something, I figured in this case it's easiest to ask developers to
>> > manually delete their local glog, and then bin/bootstrap_toolchain.py
>> will
>> > download the most recent glog that's built against gflag. This is a
>> > one-time thing.
>> >
>> > I'll send out instructions about how to do this when the toolchain is
>> > updated.
>> >
>>
>
>
>
> --
> Henry Robinson
> Software Engineer
> Cloudera
> 415-994-6679 <(415)%20994-6679>
>

Re: Heads-up - manual toolchain update required soon

[Henry Robinson]

Let's do it individually. I'll push an update patch for my change now.

On 14 May 2017 at 06:09, Lars Volker  wrote:

> I recently bumped the Breakpad version in the toolchain repo and now would
> like to pull that into master. The change to do so is here:
> https://gerrit.cloudera.org/#/c/6883/
>
> Should I wait until gflags has been pulled into master and rebase? Or would
> you like me to bump gflags in my change, too?
>
> On Tue, May 9, 2017 at 12:21 AM, Henry Robinson  wrote:
>
> > I'm about to start the process of getting IMPALA-5174 committed to the
> > toolchain. This patch changes gflags to allow 'hidden' flags that won't
> > show up on /varz etc.
> >
> > The toolchain glog has a dependency on gflags, meaning that the installed
> > glog library needs to be built against the installed gflag library. So
> when
> > the new gflag gets pulled in, you will need the new glog as well.
> >
> > However, the toolchain scripts won't detect that anything has changed for
> > glog, because there's no version number change (changing the toolchain
> > build ID doesn't cause the toolchain scripts to invalidate dependencies).
> >
> > Rather than introduce a spurious version bump with an empty patch file or
> > something, I figured in this case it's easiest to ask developers to
> > manually delete their local glog, and then bin/bootstrap_toolchain.py
> will
> > download the most recent glog that's built against gflag. This is a
> > one-time thing.
> >
> > I'll send out instructions about how to do this when the toolchain is
> > updated.
> >
>



-- 
Henry Robinson
Software Engineer
Cloudera
415-994-6679

Re: Heads-up - manual toolchain update required soon

[Lars Volker]

I recently bumped the Breakpad version in the toolchain repo and now would
like to pull that into master. The change to do so is here:
https://gerrit.cloudera.org/#/c/6883/

Should I wait until gflags has been pulled into master and rebase? Or would
you like me to bump gflags in my change, too?

On Tue, May 9, 2017 at 12:21 AM, Henry Robinson  wrote:

> I'm about to start the process of getting IMPALA-5174 committed to the
> toolchain. This patch changes gflags to allow 'hidden' flags that won't
> show up on /varz etc.
>
> The toolchain glog has a dependency on gflags, meaning that the installed
> glog library needs to be built against the installed gflag library. So when
> the new gflag gets pulled in, you will need the new glog as well.
>
> However, the toolchain scripts won't detect that anything has changed for
> glog, because there's no version number change (changing the toolchain
> build ID doesn't cause the toolchain scripts to invalidate dependencies).
>
> Rather than introduce a spurious version bump with an empty patch file or
> something, I figured in this case it's easiest to ask developers to
> manually delete their local glog, and then bin/bootstrap_toolchain.py will
> download the most recent glog that's built against gflag. This is a
> one-time thing.
>
> I'll send out instructions about how to do this when the toolchain is
> updated.
>

Heads-up - manual toolchain update required soon

[Henry Robinson]

I'm about to start the process of getting IMPALA-5174 committed to the
toolchain. This patch changes gflags to allow 'hidden' flags that won't
show up on /varz etc.

The toolchain glog has a dependency on gflags, meaning that the installed
glog library needs to be built against the installed gflag library. So when
the new gflag gets pulled in, you will need the new glog as well.

However, the toolchain scripts won't detect that anything has changed for
glog, because there's no version number change (changing the toolchain
build ID doesn't cause the toolchain scripts to invalidate dependencies).

Rather than introduce a spurious version bump with an empty patch file or
something, I figured in this case it's easiest to ask developers to
manually delete their local glog, and then bin/bootstrap_toolchain.py will
download the most recent glog that's built against gflag. This is a
one-time thing.

I'll send out instructions about how to do this when the toolchain is
updated.