Find the answer to your Linux question:
Results 1 to 6 of 6
.................... make[1]: Leaving directory `/home/notroot/gcc-4.0.0/fixincludes' make[1]: Entering directory `/home/notroot/gcc-4.0.0/intl' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/notroot/gcc-4.0.0/intl' make[1]: Entering directory `/home/notroot/gcc-4.0.0/build-i686-pc-linux-gnu/libiberty' make[1]: *** No rule to make ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Engineer
    Join Date
    Jan 2005
    Location
    Chicago (USA)
    Posts
    1,028

    GCC4.0.0


    ....................
    make[1]: Leaving directory `/home/notroot/gcc-4.0.0/fixincludes'
    make[1]: Entering directory `/home/notroot/gcc-4.0.0/intl'
    make[1]: Nothing to be done for `all'.
    make[1]: Leaving directory `/home/notroot/gcc-4.0.0/intl'
    make[1]: Entering directory `/home/notroot/gcc-4.0.0/build-i686-pc-linux-gnu/libiberty'
    make[1]: *** No rule to make target `../include/ansidecl.h', needed by `regex.o'. Stop.
    make[1]: Leaving directory `/home/notroot/gcc-4.0.0/build-i686-pc-linux-gnu/libiberty'
    make: *** [all-build-libiberty] Error 2
    [notroot@localhost gcc-4.0.0]$

    That happens when I run make (after ./configure, of course)

    make bootstrap gives

    [notroot@localhost gcc-4.0.0]$ make bootstrap
    make[1]: Entering directory `/home/notroot/gcc-4.0.0/build-i686-pc-linux-gnu/libiberty'
    make[1]: *** No rule to make target `../include/ansidecl.h', needed by `regex.o'. Stop.
    make[1]: Leaving directory `/home/notroot/gcc-4.0.0/build-i686-pc-linux-gnu/libiberty'
    make: *** [all-build-libiberty] Error 2
    [notroot@localhost gcc-4.0.0]$

  2. #2
    Just Joined!
    Join Date
    May 2005
    Posts
    1

    make: *** No rule to make target `../include/ansidecl.h',

    make: *** No rule to make target `../include/ansidecl.h', needed by `regex.o'
    did anyone happen to resolve this problem?

    this is currently a problem in 4.0.0 and 4.1.0. Help

  3. #3
    Linux Engineer
    Join Date
    Jan 2005
    Location
    Chicago (USA)
    Posts
    1,028
    bump

  4. #4
    Just Joined!
    Join Date
    May 2005
    Posts
    8
    i'm getting the same problem......

  5. #5
    Just Joined!
    Join Date
    May 2005
    Posts
    1

    solution

    Apparently you need to build in a seperate directory. E.g. :

    cd gcc-4.0.0
    mkdir obj
    cd obj
    ../configure

    (the gcc-4.0.0 directory must be removed and extracted again if you already ran ./configure in the gcc-4.0.0 directory)

  6. #6
    Just Joined!
    Join Date
    Apr 2005
    Location
    Belarus
    Posts
    14
    Dont you think it's too early to use GCC 4.0.0
    it is not so well tested so it _may_ produce some errors that could be unobvious...
    i suppose we should wait at least for a couple of weeks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •