Opened 5 years ago

Last modified 2 months ago

#21532 new enhancement

Create SAGE_LOCAL directory hierarchy during "make", not "configure"

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-9.5
Component: build Keywords:
Cc: jdemeyer Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


./configure should not create the directory hierarchy under SAGE_LOCAL.

Normally this is the task of make install; but since our make already does the equivalent of "make install" (see #21479 and #21495 for discussion), we should do this during make.

. . .

A possible implementation would be to use the currently unused automake-generated build/make/Makefile-auto to do that by calling make -f Makefile-auto install during make.

Change History (6)

comment:1 Changed 4 years ago by embray

This also creates problems with $SAGE_SUDO and --prefix= set to a root-owned directory, since it effectively means we have to run ./configure as root. I agree it would be better to do in the Makefile, and run the relevant commands with $SAGE_SUDO.

comment:2 Changed 20 months ago by embray

  • Milestone changed from sage-7.5 to sage-wishlist

comment:3 Changed 17 months ago by mkoeppe

  • Milestone changed from sage-wishlist to sage-9.2

Moving some tickets to 9.2. This is not a promise that I will be working on them.

comment:4 Changed 11 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:5 Changed 8 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

comment:6 Changed 2 months ago by mkoeppe

  • Milestone changed from sage-9.4 to sage-9.5
Note: See TracTickets for help on using tickets.