Re: Errors with checkinstall

[Juan Pablo Carbajal]

On Mon, Feb 27, 2012 at 6:18 PM, Rik <address@hidden> wrote:
> On 02/27/2012 01:18 AM, address@hidden wrote:
>> Message: 7
>> Date: Mon, 27 Feb 2012 09:53:44 +0100
>> From: Juan Pablo Carbajal <address@hidden>
>> To: address@hidden, Octave Maintainers
>>       <address@hidden>
>> Subject: 3.6.1 can't use checkinstall
>> Message-ID:
>>       <address@hidden>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi,
>>
>> I downloaded the tar pointed from octave.org. It compiles and checks
>> gives zero erros. However when I run
>> sudo checkinstall
>> I get the error
>>
>> test -z "/usr/local/include/octave-3.6.1/octave" || /bin/mkdir -p
>> "/usr/local/include/octave-3.6.1/octave"
>> /bin/mkdir: cannot create directory `/usr/local/include/octave-3.6.1':
>> No such file or directory
>> make[3]: *** [install-octincludeHEADERS] Error 1
>> make[3]: Leaving directory
>> `/home/juanpi/Resources/3rdPartyCode/octave-3.6.1/libcruft'
>> make[2]: *** [install-am] Error 2
>> make[2]: Leaving directory
>> `/home/juanpi/Resources/3rdPartyCode/octave-3.6.1/libcruft'
>> make[1]: *** [install-recursive] Error 1
>> make[1]: Leaving directory `/home/juanpi/Resources/3rdPartyCode/octave-3.6.1'
>> make: *** [install] Error 2
>>
>> What does the error mean?
> 2/27/12
>
> Juan,
>
> It works for me on Kubuntu 10.04.  I can do 'sudo make install' or 'sudo
> checkinstall make install' and both succeed.  The error message is pretty
> clear that it can't create the directory in question.  Since you used sudo
> I don't think it is a permissions issue.  It might be a problem with
> 'mkdir'.  Some mkdir do not support the '-p' option.  You could test that
> with 'mkdir -p ~/foo1/foo2/foo3' which should create a 3-deep directory
> structure.
>
> For reference from my machine:
>
> dpkg -S /bin/mkdir
> coreutils: /bin/mkdir
> dpkg -l coreutils
> ii  coreutils                   7.4-2ubuntu3                The GNU core
> utilities
>
> --Rik
>

Rik,
Thank you very much for answering. My mkdir works fine with the -p
flag. I checked with your example.
I found that the problem is highly 10.10 related and is due to an
option in checkinstall about translations.
So
sudo checkinstall --fstrans=no

solves the problem.


-- 
M. Sc. Juan Pablo Carbajal
-----
PhD Student
University of Zürich
http://ailab.ifi.uzh.ch/carbajal/