Discussion related to cado-nfs

[Pierrick Gaudry <pierrick.gaudry@loria.fr>]

On Wed, Jul 06, 2016 at 01:26:01PM +0300, Владимир Мартьянов wrote:
> Hello!
> 
> I'm testing cado-nfs on multiple mcahines. I started a master server, it
> works fine. Then I tried to connect slave to it and I got error message on
> both master and slave: "download/polyselect:
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not
> found (required by download/polyselect)". I tried to understand what
> happened and realised: cado-nfs/build/cado-nfs/polyselect was copied to the
> slave machine and started there!
> 
> For me it's strange: master and slave could have different architectures,
> library versions and so on. Is it a bug or feature? And how could I bypass
> this behavior?

It is a feature, but I tend to see it as a bug, indeed.

Anyway, when you start a client, you can use the --bindir option of the
cado-nfs-client.py script to tell where to find the binaries to use
instead of having them downloaded from the server.

Pierrick