Uploaded image for project: 'Couchbase Python Client Library'
  1. Couchbase Python Client Library
  2. PYCBC-966

Build Support for Ubuntu 20.04 LTS

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.1.3
    • library

    Description

      We need to support Ubuntu 20.04 LTS for which is scheduled to be released April 23, 2020 since Ubuntu 16.04 LTS EOL is April 1, 2021 and will be deprecated.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            david.kelly David Kelly added a comment -

            Omer Katz When pip builds couchbase (the c extension in particular), it uses the gcc you have in the path. In a shell where you are logged in as the user that created the builds in those logs above (which say gcc 5.5.0), I'd just do gcc --version and see what it says. Also which gcc will tell you where gcc is. Probably that will be /usr/bin/gcc, and it will be a symbolic link to the real gcc. My guess is that symbolic link will be pointing to gcc-5.

            Also, I believe there's an environment variable COMPILER_PATH which could complicate matters, but I've never used it. I didn't see that echoed in the build logs, but thought worth mentioning just in case.

            david.kelly David Kelly added a comment - Omer Katz When pip builds couchbase (the c extension in particular), it uses the gcc you have in the path. In a shell where you are logged in as the user that created the builds in those logs above (which say gcc 5.5.0), I'd just do gcc --version and see what it says. Also which gcc will tell you where gcc is. Probably that will be /usr/bin/gcc , and it will be a symbolic link to the real gcc. My guess is that symbolic link will be pointing to gcc-5. Also, I believe there's an environment variable COMPILER_PATH which could complicate matters, but I've never used it. I didn't see that echoed in the build logs, but thought worth mentioning just in case.
            jared.casey Jared Casey added a comment -

            FYI – 3.1.3 was release today.

            jared.casey Jared Casey added a comment - FYI – 3.1.3 was release today.
            the_drow Omer Katz added a comment -

            David Kelly gcc --version says gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0 and it is symlinked to gcc-10.

            I'm not sure where gcc 5 is picked up from but I think this is a bug in your build system.

            My machine is using ccache as the compiler.

            the_drow Omer Katz added a comment - David Kelly gcc --version says gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0 and it is symlinked to gcc-10. I'm not sure where gcc 5 is picked up from but I think this is a bug in your build system. My machine is using ccache as the compiler.
            david.kelly David Kelly added a comment -

            our build system doesn't download and install gcc. All our build systems, my Debian 10 box, several ubuntu 20.04 images I have used all pickup the intended gcc.

            If you were building on some other image (say, a manylinux image), I'd expect that image to have an older gcc (like 5 or 4.8 or something – IDK exactly what) as that's how it maintains compatibility across the many linux out there, I believe.

            In any case, this can't be our build pulling in some compiler you don't have installed and in the path somehow, AFAICT.

            david.kelly David Kelly added a comment - our build system doesn't download and install gcc. All our build systems, my Debian 10 box, several ubuntu 20.04 images I have used all pickup the intended gcc. If you were building on some other image (say, a manylinux image), I'd expect that image to have an older gcc (like 5 or 4.8 or something – IDK exactly what) as that's how it maintains compatibility across the many linux out there, I believe. In any case, this can't be our build pulling in some compiler you don't have installed and in the path somehow, AFAICT.
            the_drow Omer Katz added a comment -

            I'm not saying that. I am saying that your build system detects the compiler version incorrectly somehow.

            Try compiling the package with $(brew --prefix)/bin in your PATH with both gcc and ccache installed by brew and see this for yourself.

            the_drow Omer Katz added a comment - I'm not saying that. I am saying that your build system detects the compiler version incorrectly somehow. Try compiling the package with $(brew --prefix)/bin in your PATH with both gcc and ccache installed by brew and see this for yourself.

            People

              david.kelly David Kelly
              arun.vijayraghavan Arun Vijayraghavan (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty