New x86-64/amd64 packages for VGL 2.5.1 and later were uploaded last night. Apparently the Docker image I had been using since 2016 to build official VirtualGL binaries didn't have the x86-64 version of libstdc++.a installed, so those binaries all depended on libstdc++.so.6 and were thus not cross-compatible (i.e. they probably only worked with certain Linux flavors.) Other than changing the libstdc++ dependency to static rather than dynamic, there should be no other differences in these new packages.
Whenever I upload new binaries to correct problems such as this, I will always update the README in the SourceForge files directory (e.g. https://sourceforge.net/projects/virtualgl/files/2.6/) with information about which packages were replaced, the date of replacement, and the reason for it. All of our Linux packages are signed with GPG, also (https://virtualgl.org/Downloads/DigitalSignatures). DRC On 4/11/19 1:46 PM, Daniele wrote: > Hi, > > I have a Dockerfile that downloads virtualgl_2.6.deb and checks the hash > for security. Recently, in the last 12 hrs, the file seems to have > changed, is this intended? What are the changes? > > Note: yes, I should probably change the Dockerfile to check signatures > instead. For now, I did that manually and it's fine, so I'm just curious ... > > Thanks! > Daniele -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/60f5c8b1-094d-f546-58a7-612afd0a582c%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
