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.

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



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



  • 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.



  • @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.



  • @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?



  • @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.



  • @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?



  • @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.



Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.