On Fri, Dec 07, 2018 at 01:47:44PM -0500, rhkramer@gmail.com wrote: > On Thursday, December 06, 2018 10:42:48 PM Roberto C. Sánchez wrote: > > As far as what you do next, it should be sufficient to have him swap > > '-lstdc++' for '-static-libstdc++' and then rebuild. That should get > > you a working binary. > > Thanks! > > The programmer did what you suggested and that binary works for me on my > Jessie system. Eventually I will try it on my Wheezy system. > > I do plan to continue with some of the other suggestions made in this thread > (like the ones to create a chroot and then compile there, and then maybe to > play with some virtual machines). [...] Note that if the build is "just a chroot away" (meaning that you just need other, possibly incopatible library versions, but not another kernel, for example) schroot (a wrapper around chroot) or sbuild (a Debian package builder in a chroot) might ease your work a bit. Including cross-building of packages for different architectures, with the help of QEMU. Either your developer sets things up to deliver a binary (or a Debian package) fit for your box or you test things (as you did now) things prepared for your developer's box. > now I find that learning and trying new things is often a stressful experience > (which, among other things, leads to bad eating habits). Accept that learning takes time. Loads of it. Cheers -- t
Attachment:
signature.asc
Description: Digital signature