Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
mkoeppe opened this issue Sep 18, 2016 · 3 comments
Open

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

mkoeppe opened this issue Sep 18, 2016 · 3 comments
Labels
c: build p: major / 3 t: enhancement

Comments

@mkoeppe
Copy link
Member

mkoeppe commented Sep 18, 2016

./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.

CC: @jdemeyer

Component: build

Issue created by migration from https://trac.sagemath.org/ticket/21532
@mkoeppe mkoeppe added this to the sage-7.5 milestone Sep 18, 2016
@embray
Copy link
Contributor

embray commented Feb 5, 2018

comment:1

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.

@embray embray removed this from the sage-7.5 milestone Feb 5, 2020
@mkoeppe
Copy link
Member Author

mkoeppe commented May 1, 2020

comment:3

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

@mkoeppe mkoeppe added this to the sage-9.2 milestone May 1, 2020
@mkoeppe mkoeppe modified the milestones: sage-9.2, sage-9.3 Oct 24, 2020
@mkoeppe
Copy link
Member Author

mkoeppe commented Feb 13, 2021

comment:5

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

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Feb 13, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.4, sage-9.5 Jul 19, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.5, sage-9.6 Dec 14, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.6, sage-9.7 Mar 5, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.7, sage-9.8 Aug 31, 2022
@mkoeppe mkoeppe removed this from the sage-9.8 milestone Jan 29, 2023
@mkoeppe mkoeppe mentioned this issue Jan 29, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: build p: major / 3 t: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@embray @mkoeppe