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

Linker cannot find custom libzfs location like it can with header files

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • 3
    • 14044

    Description

      M4 files missing a -L option for custom libzfs.

      See Brian's comments on http://review.whamcloud.com/#/c/10193/6

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. LU-5091 LU-4606 breaks --with-zfs-devel option

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-5091 LU-4606 breaks --with-zfs-devel option

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-4606 Lustre hard codes libzfs.so.1 in lustre/utils/mount_utils_zfs.c

          • Major - Major loss of function.
          • Resolved

          Activity

            [LU-5096] Linker cannot find custom libzfs location like it can with header files
            simmonsja James A Simmons added a comment -

            Sorry I misread the ticket. I was under the impression that the code for LU-3497 some how got removed by accident. Sorry I haven't looked into the details. My bad.

            simmonsja James A Simmons added a comment - Sorry I misread the ticket. I was under the impression that the code for LU-3497 some how got removed by accident. Sorry I haven't looked into the details. My bad.
            brian Brian Murrell (Inactive) added a comment -

            simmonsja: No, LU-5091 is about linking the library. I know, because I opened it. The work for using --with-zfs-devel to find the headers is already landed a while ago in LU-3497.

            brian Brian Murrell (Inactive) added a comment - simmonsja : No, LU-5091 is about linking the library. I know, because I opened it. The work for using --with-zfs-devel to find the headers is already landed a while ago in LU-3497 .
            simmonsja James A Simmons added a comment -

            LU-5091 is for headers and this is for linking the library. Yes they could be combined into one patch.

            simmonsja James A Simmons added a comment - LU-5091 is for headers and this is for linking the library. Yes they could be combined into one patch.
            brian Brian Murrell (Inactive) added a comment -

            Is this a duplicate of LU-5091? It seems so but I don't want to just assume.

            brian Brian Murrell (Inactive) added a comment - Is this a duplicate of LU-5091 ? It seems so but I don't want to just assume.

            People

              utopiabound Nathaniel Clark
              utopiabound Nathaniel Clark
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: