/bin/sh: -chmod: command not found

poma pomidorabelisima at gmail.com
Mon Feb 3 01:29:02 UTC 2014


On 03.02.2014 01:46, Ralf Corsepius wrote:
> On 02/03/2014 01:34 AM, poma wrote:
>> What's the better way to deal with this phenomenon?
> 
> The first step would be to build verbose such that you see where the 
> error actually occurs.
> 
>>>> Making all in api
>> make[4]: Entering directory
>> `/home/poma/rpmbuild/BUILD/ModemManager-1.2.0/docs/reference/api'
>>    DOC   Preparing build
>>    DOC   Scanning header files
>>    DOC   Introspecting gobjects
>>    DOC   Rebuilding template files
>>    DOC   Building XML
>> /bin/sh: -chmod: command not found
>>    DOC   Building HTML
>>    DOC   Fixing cross-references
>> make[4]: Leaving directory
>> `/home/poma/rpmbuild/BUILD/ModemManager-1.2.0/docs/reference/api'
>> Making all in libmm-glib
>> make[4]: Entering directory
>> `/home/poma/rpmbuild/BUILD/ModemManager-1.2.0/docs/reference/libmm-glib'
>>    DOC   Preparing build
>>    DOC   Scanning header files
>>    DOC   Introspecting gobjects
>>    DOC   Rebuilding template files
>>    DOC   Building XML
>> /bin/sh: -chmod: command not found
>>    DOC   Building HTML
>>    DOC   Fixing cross-references
> In general "/bin/sh: -chmod" indicates a makefile fragment is being 
> invoked as shell code instead of "make"-code.
> 
> One classical cause would be using leading spaces instead of a leading 
> tab in a makefile.
> 
> Ralf
> 

OK, thanks.


poma



More information about the test mailing list