Hello, I tried to do a "./configure && make" in freebsd an got an error during make. If I use GNU make instead it works. I attach the error output from the make command and the generated Makefile.
regards, Nikos
Nikos Mavrogiannopoulos nmav@gnutls.org writes:
I tried to do a "./configure && make" in freebsd an got an error during make. If I use GNU make instead it works. I attach the error output from the make command and the generated Makefile.
I think the problem is that bsd make doesn't allow multiple files to b listed for a single include command. If you want to use bsd make, you have to configure with --disable-dependency-tracking. ./configure --help says
--disable-dependency-tracking Disable dependency tracking. Dependency tracking doesn't work with BSD make
Any suggestions other places to document that problem?
The Makefile.in does
DEP_FILES = $(SOURCES:.c=.$(OBJEXT).d) $(SOURCES:.c=.p$(OBJEXT).d) @DEP_INCLUDE@ $(DEP_FILES)
and "include" or "#" is substituted for @DEP_INCLUDE@, depending on whether or not dependency tracking is enabled.
Regards, /Niels
On 08/28/2011 12:06 AM, Niels Möller wrote:
I tried to do a "./configure&& make" in freebsd an got an error during make. If I use GNU make instead it works. I attach the error output from the make command and the generated Makefile.
I think the problem is that bsd make doesn't allow multiple files to b listed for a single include command. If you want to use bsd make, you have to configure with --disable-dependency-tracking. ./configure --help says
Why don't you use automake for that? The automake generated makefiles seem to be quite portable across different make programs.
regards, Nikos
Nikos Mavrogiannopoulos nmav@gnutls.org writes:
Why don't you use automake for that?
People seem to be asking that every other month...
Because I don't think it's important to be portable to all strange make programs (anyone can install gnu make). And because automake causes all sorts of nasty problems if you need to have unusual make rules to work together with the automake generated rules. I did use automake in nettle (and lsh) some years back. E.g., the "minor" change of behavior in automake to stop using suffix rules and instead generate one rule for each object file totally broke the way nettle sets up building of assembly files.
I'm *not* going to switch back to automake, and I'm not going to use libtool either.
/nisse
nettle-bugs@lists.lysator.liu.se
-
Nikos Mavrogiannopoulos -
nisse＠lysator.liu.se