There are. I tried to document the list at some point here:
https://cwiki.apache.org/confluence/display/IMPALA/Building+native-toolchain+from+scratch+and+using+with+Impala

I believe that covers most of them, but it may be slightly stale. Please
feel free to update the list or let us know if something is missing.

On Wed, Feb 14, 2018 at 1:36 PM, Quanlong Huang <huang_quanl...@126.com>
wrote:

> Are there any pre-requirements for native-toolchain? Maybe I need to
> install something first.
> I just check out the master branch and run buildall.sh. Here's more
> info in my env:
>
> $ lsb_release -a
>
> No LSB modules are available.
>
> Distributor ID: Ubuntu
>
> Description:    Ubuntu 14.04.2 LTS
>
> Release:        14.04
>
> Codename:       trusty
>
> $ cat /etc/os-release
>
> NAME="Ubuntu"
>
> VERSION="14.04.2 LTS, Trusty Tahr"
>
> ID=ubuntu
>
> ID_LIKE=debian
>
> PRETTY_NAME="Ubuntu 14.04.2 LTS"
>
> VERSION_ID="14.04"
>
> HOME_URL="http://www.ubuntu.com/";
>
> SUPPORT_URL="http://help.ubuntu.com/";
>
> BUG_REPORT_URL="
> http://bugs.launchpad.net/ubuntu/";
>
> $ uname -a
>
> Linux iadhadoop-c39 3.16.0-77-generic #99~14.04.1-Ubuntu SMP Tue Jun 28
> 19:17:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> I also attach the build log of cyrus-sasl in the attachment.
>
> Thanks,
> Quanlong
>
> At 2018-02-15 00:55:51, "Laszlo Gaal" <laszlo.g...@cloudera.com> wrote:
> >My build has progressed past the cyrus-sasl phase with no errors, so I
> >don't have a repro case handy.
> >My build env is:
> >
> >laszlog@laszlog1:~/native-toolchain$ lsb_release -a
> >No LSB modules are available.
> >Distributor ID: Ubuntu
> >Description: Ubuntu 14.04.5 LTS
> >Release: 14.04
> >Codename: trusty
> >laszlog@laszlog1:~/native-toolchain$ uname -a
> >Linux laszlog1 4.4.0-112-generic #135~14.04.1-Ubuntu SMP Tue Jan 23
> >20:41:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> >
> >
> >OTOH grepping in cyrus-sasl finds the following:
> >
> >laszlog@laszlog1:~/native-toolchain/source/cyrus-sasl/cyrus-sasl-2.1.23$
> >find . -name "*.c" -exec fgrep -n 'NULL, DB_HASH, flags, 0660' {} \;
> >104: ret = (*mbdb)->open(*mbdb, NULL, path, NULL, DB_HASH, flags, 0660);
> >106: ret = (*mbdb)->open(*mbdb, path, NULL, DB_HASH, flags, 0660);
> >
> >
> >
> >(this is in *sasldb/db_berkeley.c*, starting on *line 103*):
> >
> >#if DB_VERSION_MAJOR == 4 && DB_VERSION_MINOR >= 1
> >        ret = (*mbdb)->open(*mbdb, NULL, path, NULL, DB_HASH, flags, 0660);
> >#else
> >        ret = (*mbdb)->open(*mbdb, path, NULL, DB_HASH, flags, 0660);
> >#endif
> >
> >
> >so DB_VERSION_MAJOR may have a wrong value in your build -- but admittedly
> >I don't know what could influence that value.
> >
> >Could you post the command line you used to start the build, to see if
> >there could have been extra settings impacting the build?
> >
> >On Wed, Feb 14, 2018 at 3:06 PM, Quanlong Huang <huang_quanl...@126.com>
> >wrote:
> >
> >> Thank you, Laszlo! I build the master branch.
> >>
> >>
> >> At 2018-02-14 21:47:48, "Laszlo Gaal" <laszlo.g...@cloudera.com> wrote:
> >> >Hey Quanlong,
> >> >
> >> >I have made a couple of minor changes, focusing on how our (Cloudera's)
> >> >internal automation drives the toolchain build.
> >> >I did not expect these changes to break you; I'll look into it shortly;
> >> >I'll keep you updated.
> >> >
> >> >Which branch dod you try to build? Was is "master"?
> >> >
> >> >Thanks,
> >> >
> >> >    - Laszlo
> >> >
> >> >On Wed, Feb 14, 2018 at 1:03 PM, Quanlong Huang <huang_quanl...@126.com>
> >> >wrote:
> >> >
> >> >> Hi all,
> >> >>
> >> >>
> >> >> The build of cyrus-sasl-2.1.23 failed in my env. The errors are all in
> >> the
> >> >> db_berkeley.c:
> >> >>
> >> >>
> >> >>
> >> >> db_berkeley.c:106:8: error: too few arguments to function
> >> '(*mbdb)->open'
> >> >>
> >> >>   ret = (*mbdb)->open(*mbdb, path, NULL, DB_HASH, flags, 0660);
> >> >>
> >> >>         ^
> >> >>
> >> >> make[2]: *** [db_berkeley.lo] Error 1
> >> >>
> >> >>
> >> >>
> >> >> I'm using Ubuntu 14.04.2. It used to build success months ago. Are there
> >> >> any changes relate to this?
> >> >>
> >> >>
> >> >> Thanks,
> >> >> Quanlong
> >>
>
>

Reply via email to