[asterisk-bugs] [Asterisk 0016781]: make install fails when GNU install missing

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Feb 5 18:46:20 CST 2010


The following issue has been SUBMITTED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16781 
====================================================================== 
Reported By:                bklang
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16781
Category:                   Core/Portability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 245148 
Request Review:              
====================================================================== 
Date Submitted:             2010-02-05 18:46 CST
Last Modified:              2010-02-05 18:46 CST
====================================================================== 
Summary:                    make install fails when GNU install missing
Description: 
I am marking this as a portability bug.  Even though this problem could
exist on Linux, the fact that the "install" binary is provided by GNU
coreutils means that a Linux system would have to be pretty broken not to
have it.  So this problem will only manifest on systems where coreutils is
not installed, or the "install" binary is otherwise missing.

The build system creates an install-sh drop-in replacement if the
"install" binary is missing.  However, the path to the script is referenced
as ./ which causes subdirectories to break when calling for the install-sh
script.

The variable for INSTALL is populated in makeopts so this might actually
be a problem with menuselect.  One workaround I used was to fully qualify
the path to the install-sh script.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-05 18:46 bklang         New Issue                                    
2010-02-05 18:46 bklang         Asterisk Version          => SVN             
2010-02-05 18:46 bklang         Regression                => No              
2010-02-05 18:46 bklang         SVN Branch (only for SVN checkouts, not tarball
releases) => 1.6.2           
2010-02-05 18:46 bklang         SVN Revision (number only!) => 245148          
======================================================================




More information about the asterisk-bugs mailing list