Bug 45900 - "make install" fails from read-only filesystem
Summary: "make install" fails from read-only filesystem
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Build (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-26 10:32 UTC by Philip Brown
Modified: 2008-09-26 10:32 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Brown 2008-09-26 10:32:22 UTC
For security reasons,etc, it is a generally nice thing to be able to mount
a src tree read-only from another system, then be able to type "make install" on the destination system.

This fails, with the current apache 2.2.9 src.


mv: cannot rename libaprutil-1.so.0.3.0 to libaprutil-1.so.0.3.0U: Read-only file system

in addition, having ONE system with a writeable /usr/local/src, and then mounting it read-only everywhere else, has additional problems.
I cant just copy the compiled src tree to somewhere else and do make install, because you have hardcoded the full src tree path in.
Please stop doing that. Please use relative paths, and stop having "make install" do anything but copy files from src to destination. If you must do temporary things, do it in the destination directory?

It should be noted that this sort of situation would be just as applicable, if you were doing all this on the same system, but had a "trusted" user do compiles, and an "untrusted" user doing "make install".  This would also have the src tree be read-only, while destination is writable.