Opened 5 years ago

Closed 3 years ago

#17497 closed defect (fixed)

Relocation of sage breaks compile

Reported by: ppurka Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: relocation Keywords:
Cc: Merged in:
Authors: Reviewers: Jeroen Demeyer
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by ppurka)

I relocated my sage directory from $HOME/tmp/sage to /mnt/usb/Installations/sage and it broke the compilation. In particular, I got this from libgd:

/bin/sh ../libtool --tag=CC   --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I.   -I/mnt/usb/Installations/sage/local/include/libpng12  -I/home/punarbasu/tmp/sage/local/include/freetype2   -g -march=native -pipe -fvisibility=hidden -MT gdft.lo -MD -MP -MF .deps/gdft.Tpo -c -o gdft.lo gdft.c
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I/mnt/usb/Installations/sage/local/include/libpng12 -I/home/punarbasu/tmp/sage/local/include/freetype2 -g -march=native -pipe -fvisibility=hidden -MT gdft.lo -MD -MP -MF .deps/gdft.Tpo -c gdft.c  -fPIC -DPIC -o .libs/gdft.o
gdft.c:153:22: fatal error: ft2build.h: No such file or directory
compilation terminated.

Looking into local/bin, I found that many configuration parameters are still set to my old directory:

~/Installations/sage» grep -m1 '/home/punarbasu/tmp/sage' local/bin/* | wc -l
140

Change History (8)

comment:1 Changed 5 years ago by ppurka

  • Description modified (diff)

comment:2 Changed 5 years ago by fbissey

There was someone else with a strangely similar problem on the list the other day. I think I may have turned them off. In any case what is the content of local/lib/pkgconfig/freetype2.pc? I think the relocation script is supposed to modify it but I suspect it doesn't happen.

comment:3 Changed 5 years ago by jdemeyer

I think relocation during a build has never been really supported. Relocation is mostly meant to move an already-compiled Sage installation.

comment:4 Changed 5 years ago by fbissey

Jeroen is right. I don't think there is anything to make that work if you stop in the middle of the compilation. make distclean is probably your only hope to get a compilation in that case.

comment:5 Changed 5 years ago by ppurka

Well, my installation was pretty well nigh broken. I deleted it and installed a new one from scratch. You can close this ticket if you don't plan to fix this relocation problem.

BTW, I don't understand what you mean by "relocation during a build". What I did was:

  1. Already had develop branch compiled and installed in ~/tmp/sage
  2. Copied my whole sage installation to /mnt/usb/Installations/sage and ran sage so that the relocation is performed.
  3. Ran sage upgrade to upgrade to the latest develop branch.

I wasn't changing folders half-way through a develop upgrade. I suspect this can be fixed by fixing the (text) files in SAGE_ROOT/local/bin, but my installation was quite badly broken so I decided to start afresh.

comment:6 Changed 3 years ago by jdemeyer

  • Milestone changed from sage-6.5 to sage-duplicate/invalid/wontfix
  • Reviewers set to Jeroen Demeyer
  • Status changed from new to needs_review

Relocation is no longer supported.

comment:7 Changed 3 years ago by jdemeyer

  • Status changed from needs_review to positive_review

comment:8 Changed 3 years ago by vbraun

  • Resolution set to fixed
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.