Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-6547

build errors building against recent 4.1-rc1 kernel on Ubuntu 15.04 building linux-tracefile

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • None
    • None
    • 1
    • 9223372036854775807

    Description

      Building against a recent kernel the -Werror option in the Rules file is catching a re-definition of CONFIG_LNET_MAX_PAYLOAD and causing the build to fail.

      make[3]: Entering directory '/usr/src/linux-headers-4.1.0-rc1+'
      LD /home/king/lustre/lustre-release/built-in.o
      LD /home/king/lustre/lustre-release/libcfs/built-in.o
      LD /home/king/lustre/lustre-release/libcfs/libcfs/built-in.o
      CC [M] /home/king/lustre/lustre-release/libcfs/libcfs/linux/linux-tracefile.o
      In file included from <command-line>:0:0:
      /home/king/lustre/lustre-release/config.h:26:0: error: "CONFIG_LNET_MAX_PAYLOAD" redefined [-Werror]
      #define CONFIG_LNET_MAX_PAYLOAD LNET_MTU
      ^
      In file included from /usr/src/linux-headers-4.1.0-rc1+/include/linux/kconfig.h:4:0,
      from <command-line>:0:
      include/generated/autoconf.h:4174:0: note: this is the location of the previous definition
      #define CONFIG_LNET_MAX_PAYLOAD 1048576
      ^
      cc1: all warnings being treated as errors
      scripts/Makefile.build:258: recipe for target '/home/king/lustre/lustre-release/libcfs/libcfs/linux/linux-tracefile.o' failed

      Attachments

        Issue Links

          Activity

            [LU-6547] build errors building against recent 4.1-rc1 kernel on Ubuntu 15.04 building linux-tracefile
            pjones Peter Jones added a comment -

            ok - thanks James

            pjones Peter Jones added a comment - ok - thanks James

            All patches for Ubuntu15 support have landed. This ticket reported the same problems as LU-5628 so it can be now closed as a duplicate.

            simmonsja James A Simmons added a comment - All patches for Ubuntu15 support have landed. This ticket reported the same problems as LU-5628 so it can be now closed as a duplicate.

            Only one patch needed to support Ubuntu15 - http://review.whamcloud.com/#/c/15028

            simmonsja James A Simmons added a comment - Only one patch needed to support Ubuntu15 - http://review.whamcloud.com/#/c/15028
            simmonsja James A Simmons added a comment - The need the following patches applied to master to run on Ubuntu15: http://review.whamcloud.com/#/c/14598 http://review.whamcloud.com/#/c/14669 http://review.whamcloud.com/#/c/14683 http://review.whamcloud.com/#/c/14681 http://review.whamcloud.com/#/c/15028 http://review.whamcloud.com/#/c/14624
            simmonsja James A Simmons added a comment - - edited

            I have submitted all the patches needed to support Ubuntu15 now. With those patches also kernels up to 4.0 are supported.

            Colin do you have a gerrit account so I can add you to review the patches needed.

            simmonsja James A Simmons added a comment - - edited I have submitted all the patches needed to support Ubuntu15 now. With those patches also kernels up to 4.0 are supported. Colin do you have a gerrit account so I can add you to review the patches needed.

            I have submitted a bunch of patches for Ubuntu15 support. Only thing left is handle filldir_t api changes and generic_file_aio_XX changes.

            simmonsja James A Simmons added a comment - I have submitted a bunch of patches for Ubuntu15 support. Only thing left is handle filldir_t api changes and generic_file_aio_XX changes.

            Yep, its the tip of the iceberg. If you want to build the intel branch against 4.1-rc1 you will a bunch more patches just to make it work. See LU-6215 for details about that work.

            simmonsja James A Simmons added a comment - Yep, its the tip of the iceberg. If you want to build the intel branch against 4.1-rc1 you will a bunch more patches just to make it work. See LU-6215 for details about that work.
            green Oleg Drokin added a comment -

            The problem at hand is you probably have lustre configured i nthe kernel as a module or something, and this is not supported due to all sort of symbol clases, I suspect this is just a tip of the iceberg you are seeing here.

            If you want to build out of tree lustre, the in-tree lustre client should be disabled.

            green Oleg Drokin added a comment - The problem at hand is you probably have lustre configured i nthe kernel as a module or something, and this is not supported due to all sort of symbol clases, I suspect this is just a tip of the iceberg you are seeing here. If you want to build out of tree lustre, the in-tree lustre client should be disabled.

            People

              wc-triage WC Triage
              colinianking Colin Ian King
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: