#1 configure generates unvalid makefiles


On my SGI O2 running IRIX 6.5.6m configure produces incorrect makefiles, here's an example:

roaldp 234% make
cd . \ && CONFIG_FILES= CONFIG_HEADERS=config.h \ /bin/sh ./config.status
creating config.h
config.h is unchanged
make all-recursive
Making all in btree
make: file `Makefile' line 195: Syntax error
*** Error code 1 (bu21)
*** Error code 1 (bu21)
roaldp 235%

line 195 of the Makefile looks like:

DEPS_MAGIC := $(shell mkdir .deps > /dev/null 2>&1 || :)

It's an easy fix to remove the "=" but it would be nice if it worked from the start.


  • Roald Lygre

    Roald Lygre - 2000-01-28

    I logged the above. I suppose it should have said \"invalid\" instead of \"unvalid\"...:-)

  • Roald Lygre

    Roald Lygre - 2000-02-03

    The fix to the above, plus the fact that the compile failed due to missing path to include files can be seen from this diff of the Makefile.in in the directory \"btree\":

    diff Makefile.in.orig Makefile.in

    > .c.o:
    > $(COMPILE) -c $<
    < DEPS_MAGIC := $(shell mkdir .deps > /dev/null 2>&1 || :)
    > DEPS_MAGIC = $(shell mkdir .deps > /dev/null 2>&1 || :) -include $(DEP_FILES)
    < -include $(DEP_FILES)

  • Marc Nozell

    Marc Nozell - 2000-11-07
    • assigned_to: nobody --> nozell
    • status: Error - status not found --> open-works-for-me
  • Marc Nozell

    Marc Nozell - 2000-11-07

    Is this still a problem in 3.0.5 or the current CVS snapshot?

    On my Linux/Intel box I don't see any reference to DEPS_MAGIC
    in any of the Makefile* files.

  • Marc Nozell

    Marc Nozell - 2000-12-04

    There has been some changes in build wrt deps. Can you try the
    current version in CVS?


  • Rob Fugina

    Rob Fugina - 2001-01-08

    Is this still a problem? I don't know how the patch
    on Makefile.in should be applied to Makefile.am.
    (Makefile.in is generated by automake with Makefile.am)

  • Matthew Emmerton

    • status: open-works-for-me --> closed-works-for-me
  • Matthew Emmerton

    • labels: 100100 --> Make,autoconf
  • Matthew Emmerton

    Logged In: YES

    It looks like the user is compiling using 'make',
    not 'gmake'. I get similar errors on my FreeBSD boxes when
    using the wrong make.

    LifeLines requires gmake to build.


Log in to post a comment.