Error while compiling apache APR make file not found

21,001

Solution 1

Edit your configure file

Change the line

$RM "$cfgfile"

to

$RM -f "$cfgfile"

This will resolve the error

rm: cannot remove `libtoolT': No such file or directory

Then try run configure. That's it

Solution 2

Just running:

touch libtoolT

is sufficient to get it to build correctly. If you really want to edit the configure file to avoid the delete you can do that, but giving it a file to remove works too.

Solution 3

On apr-1.5.1 ,edit line 30145 of configure from

i.e bash# vi +30145 configure

$RM "$cfgfile"

to

$RM -f "$cfgfile"

Share:
21,001
confile
Author by

confile

Java, GWT, JavaScript, Grails, Groovy, Swift, Objective-C, iOS

Updated on July 06, 2020

Comments

  • confile
    confile almost 4 years

    I tried to compile apache APR. The instruction sayed:

    All you should have to do is this:

     ./configure
      make
      make install
    

    After ./compile I get the following output:

    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating include/apr.h
    config.status: creating build/apr_rules.mk
    config.status: creating build/pkg/pkginfo
    config.status: creating apr-1-config
    config.status: creating apr.pc
    config.status: creating test/Makefile
    config.status: creating test/internal/Makefile
    config.status: creating include/arch/unix/apr_private.h
    config.status: executing libtool commands
    rm: cannot remove `libtoolT': No such file or directory
    config.status: executing default commands
    config.status: include/apr.h is unchanged
    config.status: include/arch/unix/apr_private.h is unchanged
    

    When I try to do "make" the make file could not be found:

    -bash: make: command not found
    

    What is wrong here?

  • confile
    confile over 10 years
    well there is another bug see: stackoverflow.com/questions/18092461/…
  • c0rp
    c0rp over 8 years
    Why this bug is still there?
  • Leo Prince
    Leo Prince over 8 years
    I think they have fixed it in latest packages.. though I didnt checked it in recent past.
  • Don Branson
    Don Branson about 8 years
    @c0rp - Good question! Just saw it in 1.5.2.