Hi all, A follow up: I ran
$ git clone https://github.com/sagemath/binary-pkg.git $ cd binary-pkg $ make bdist-sage-linux $ cd .. $ unp binary-pkg/dist/sage-9.0.beta6-Debian_GNU_Linux_9-x86_64.tar.bz2 $ cd SageMath $ ./sage (watch the patching going on) sage: from fpylll import * sage: BKZ.DEFAULT_STRATEGY_PATH b'/bulk/home/malb/software/SageMath/local/share/fplll/strategie' print(load_strategies_json(b"/home/malb/projects/lattices/fplll/strategies/default.json")[60]) Strategy< 60, (40), 0.29-0.50> So the patching thing does seem to work when I do it locally. Cheers, Martin Martin R. Albrecht <martinralbre...@googlemail.com> writes: > Hi Nils, > > Thanks, this is helpful. > > Is there a straight-forward way in which I can trigger the relocation, I’m > trying to test what goes wrong, so: > > 1/ I built sage from source, all works as expected > 2a/ I move the installation, Sage barks at me. > 2b/ However, just starting python from the relocated binary and issuing > > >>> from fpylll import * > >>> BKZ.DEFAULT_STRATEGY > > '/bulk/home/malb/software/sage-long-path-for-binary-building/local/share/fplll/strategies/default.json' > >>> print > load_strategies_json("/home/malb/projects/lattices/fplll/strategies/default.json")[60] > Strategy< 60, (40), 0.29-0.50> > > seems to work. > > 3/ How do I get the relocation script to run to see if that indeed breaks the > above code? > > Sorry, if that should be obvious. > > Cheers, > Martin > > > Nils Bruin <nbr...@sfu.ca> writes: >> If you see a difference in behaviour between binary and source >> distributions, then perhaps it's due to >> >> https://github.com/sagemath/binary-pkg/blob/master/binary_pkg/templates/relocate-once.py >> >> From what I understand, a binary distribution is originally built on a >> rather long and distinctive path, so that a search-and_replace on absolute >> path names should work (and should have enough room to make the >> replacements). Perhaps this is what goes wrong? Perhaps only part of >> fpylll's files are picked up to make replacements on? >> >> It may be worth comparing the files like bkz.so etc. on the binary install >> *before* anything was run and *after*. The mangled path names distinctly >> suggest that some path name rewrite is tried, but that it doesn't succeed >> (although the error might very well originate from your own C++ code -- >> that's not so easy for me to see). -- _pgp: https://keybase.io/martinralbrecht _www: https://malb.io -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/87mucr1pmu.fsf%40road.
