[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
automake/autoconf bug
From: |
Andrew D Jewell |
Subject: |
automake/autoconf bug |
Date: |
Mon, 10 Jun 2002 21:39:39 -0400 |
Or perhaps just a documentation oversight, if this is supposed to
happen. Or perhaps I'm missing something obvious.
It seems that mixing .c and .cc files in certain ways confuses things.
For example, take the Makefile.am
noinst_LIBRARIES = libfoo.a
libfoo_a_SOURCES = foo.c
this results in the error :
gmake[2]: *** No rule to make target `foo.cc', needed by `foo.o'. Stop.
In another iteration, I had a_bin_search.cc in the SOURCES
definition, and got an error that a_bin_search.c couldn't be made.
The weird part there is that I changed the name to abinsearch.cc and
the problem went away.
The configure.ac was about as simple as it could be :
dnl Process this file with autoconf to produce a configure script. -*-m4-*-
AC_INIT(foo, 1.2, address@hidden)
AC_CONFIG_AUX_DIR(config)
AM_CONFIG_HEADER(config.h:config.hin)
AC_CANONICAL_HOST
AM_INIT_AUTOMAKE
dnl Checks for programs.
AC_PROG_CC
AC_PROG_CPP
AC_PROG_CXX
AC_PROG_GCC_TRADITIONAL
AC_PROG_RANLIB
AC_CONFIG_FILES(
Makefile
lib/Makefile
)
AC_OUTPUT
Any help or guesses would be most appreciated.
autoconf (GNU Autoconf) 2.53
automake (GNU automake) 1.6.1
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Linux arc132.alexa.com 2.4.17-2v3 #1 Sun Apr 14 22:15:52 PDT 2002 i686 unknown
thanks,
adj
- automake/autoconf bug,
Andrew D Jewell <=