ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Raspbian and Gluster, annoyance.

    IT Discussion
    raspbian gluster version compatible
    2
    8
    894
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • travisdh1T
      travisdh1
      last edited by

      So, apparently the version of raspbian that DIY temp sensor is on, the version of gluster in the repository is 3.2.7. Which just happens to be the last version before they broke backwards compatibility, so the client on the pi can't connect to the gluster servers running 3.7.9. I'm building from source currently, and if it works, I'll post the condensed version of how I got it working.

      4 very slow cores, gcc only uses 1, gonna be a bit.

      1 Reply Last reply Reply Quote 2
      • travisdh1T
        travisdh1
        last edited by

        And looks like I'm going to just use the gluster NFS mount option as make failed on the Pi2.

        1 Reply Last reply Reply Quote 0
        • thwrT
          thwr
          last edited by

          said in Raspbian and Gluster, annoyance.:

          So, apparently the version of raspbian that DIY temp sensor is on, the version of gluster in the repository is 3.2.7. Which just happens to be the last version before they broke backwards compatibility, so the client on the pi can't connect to the gluster servers running 3.7.9. I'm building from source currently, and if it works, I'll post the condensed version of how I got it working.

          I have a cross compiler VM somewhere, but I won't have a chance to look before the next weekend.

          travisdh1T 1 Reply Last reply Reply Quote 0
          • travisdh1T
            travisdh1 @thwr
            last edited by

            @thwr said in Raspbian and Gluster, annoyance.:

            said in Raspbian and Gluster, annoyance.:

            So, apparently the version of raspbian that DIY temp sensor is on, the version of gluster in the repository is 3.2.7. Which just happens to be the last version before they broke backwards compatibility, so the client on the pi can't connect to the gluster servers running 3.7.9. I'm building from source currently, and if it works, I'll post the condensed version of how I got it working.

            I have a cross compiler VM somewhere, but I won't have a chance to look before the next weekend.

            I think the problem is that the Pi2 is 32 bit, and the programming expects 64 bit now. So, in theory, a Pi3 would work.

            thwrT 1 Reply Last reply Reply Quote 0
            • thwrT
              thwr @travisdh1
              last edited by

              @travisdh1 said in Raspbian and Gluster, annoyance.:

              @thwr said in Raspbian and Gluster, annoyance.:

              said in Raspbian and Gluster, annoyance.:

              So, apparently the version of raspbian that DIY temp sensor is on, the version of gluster in the repository is 3.2.7. Which just happens to be the last version before they broke backwards compatibility, so the client on the pi can't connect to the gluster servers running 3.7.9. I'm building from source currently, and if it works, I'll post the condensed version of how I got it working.

              I have a cross compiler VM somewhere, but I won't have a chance to look before the next weekend.

              I think the problem is that the Pi2 is 32 bit, and the programming expects 64 bit now. So, in theory, a Pi3 would work.

              Erm, can be yes. My CC build is also just 32bit, pretty sure. And the gluster stuff is 64bit arm?

              travisdh1T 1 Reply Last reply Reply Quote 0
              • travisdh1T
                travisdh1 @thwr
                last edited by

                @thwr said in Raspbian and Gluster, annoyance.:

                @travisdh1 said in Raspbian and Gluster, annoyance.:

                @thwr said in Raspbian and Gluster, annoyance.:

                said in Raspbian and Gluster, annoyance.:

                So, apparently the version of raspbian that DIY temp sensor is on, the version of gluster in the repository is 3.2.7. Which just happens to be the last version before they broke backwards compatibility, so the client on the pi can't connect to the gluster servers running 3.7.9. I'm building from source currently, and if it works, I'll post the condensed version of how I got it working.

                I have a cross compiler VM somewhere, but I won't have a chance to look before the next weekend.

                I think the problem is that the Pi2 is 32 bit, and the programming expects 64 bit now. So, in theory, a Pi3 would work.

                Erm, can be yes. My CC build is also just 32bit, pretty sure. And the gluster stuff is 64bit arm?

                The errors I was able to read during compile were complaining about variables defined as int64w, which wouldn't work so well on a 32 bit platform I don't think.

                thwrT 1 Reply Last reply Reply Quote 0
                • thwrT
                  thwr @travisdh1
                  last edited by

                  @travisdh1 said in Raspbian and Gluster, annoyance.:

                  @thwr said in Raspbian and Gluster, annoyance.:

                  @travisdh1 said in Raspbian and Gluster, annoyance.:

                  @thwr said in Raspbian and Gluster, annoyance.:

                  said in Raspbian and Gluster, annoyance.:

                  So, apparently the version of raspbian that DIY temp sensor is on, the version of gluster in the repository is 3.2.7. Which just happens to be the last version before they broke backwards compatibility, so the client on the pi can't connect to the gluster servers running 3.7.9. I'm building from source currently, and if it works, I'll post the condensed version of how I got it working.

                  I have a cross compiler VM somewhere, but I won't have a chance to look before the next weekend.

                  I think the problem is that the Pi2 is 32 bit, and the programming expects 64 bit now. So, in theory, a Pi3 would work.

                  Erm, can be yes. My CC build is also just 32bit, pretty sure. And the gluster stuff is 64bit arm?

                  The errors I was able to read during compile were complaining about variables defined as int64w, which wouldn't work so well on a 32 bit platform I don't think.

                  I can define a long int (64bit/8 bytes on most platforms) just fine on any 32bit CPU. You can even do that on a 8 or 16 bit uC. So probably the failure is somewhere else?

                  travisdh1T 1 Reply Last reply Reply Quote 0
                  • travisdh1T
                    travisdh1 @thwr
                    last edited by

                    @thwr said in Raspbian and Gluster, annoyance.:

                    @travisdh1 said in Raspbian and Gluster, annoyance.:

                    @thwr said in Raspbian and Gluster, annoyance.:

                    @travisdh1 said in Raspbian and Gluster, annoyance.:

                    @thwr said in Raspbian and Gluster, annoyance.:

                    said in Raspbian and Gluster, annoyance.:

                    So, apparently the version of raspbian that DIY temp sensor is on, the version of gluster in the repository is 3.2.7. Which just happens to be the last version before they broke backwards compatibility, so the client on the pi can't connect to the gluster servers running 3.7.9. I'm building from source currently, and if it works, I'll post the condensed version of how I got it working.

                    I have a cross compiler VM somewhere, but I won't have a chance to look before the next weekend.

                    I think the problem is that the Pi2 is 32 bit, and the programming expects 64 bit now. So, in theory, a Pi3 would work.

                    Erm, can be yes. My CC build is also just 32bit, pretty sure. And the gluster stuff is 64bit arm?

                    The errors I was able to read during compile were complaining about variables defined as int64w, which wouldn't work so well on a 32 bit platform I don't think.

                    I can define a long int (64bit/8 bytes on most platforms) just fine on any 32bit CPU. You can even do that on a 8 or 16 bit uC. So probably the failure is somewhere else?

                    Possibly, let's see if I can find that compile-time error here.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post