[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: My experiences building GNATS 4.10

From: Mike M. Volokhov
Subject: Re: My experiences building GNATS 4.10
Date: Wed, 23 Mar 2005 10:21:44 +0200

On Tue, 22 Mar 2005 16:54:39 -0500
Tim Buck <address@hidden> wrote:

> I got an error building GNATS 4.10:
>    Creating gnats-databases...
>    make: don't know how to make gnats-pwconv.o. Stop
>    *** Error code 2
>    Stop in /usr/projects/tim/gnats-4.1.0.
> This is on FreeBSD-4.9 using gcc-2.95.4. I edited gnats/Makefile
> and appended "gnats-pwconv.c" to the SOURCES line, which got me
> past this error. Then I got this one:

Yes, this (and some other) file has been missed. Is this ok to put just
all *.c files into SOURCES? I.e.:

RCS file: /cvsroot/gnats/gnats/gnats/,v
retrieving revision 1.71
diff -u -r1.71
--- 24 Feb 2005 21:21:22 -0000      1.71
+++ 23 Mar 2005 08:07:10 -0000
@@ -125,7 +125,12 @@
 #### Host-, target-, and site-specific makefiles are inserted here.
-SOURCES = btime.c cmds.c file-pr.c gen-closed-date.c gen-index.c getclose.c 
gnatsd.c pr-age.c pr-edit.c pr-stat.c query-pr.c queue-pr.c
+SOURCES = adm.c btime.c client.c cmds.c database.c edit.c fconfig.c \
+       fconfigl.c field.c file-pr.c gen-closed-date.c gen-index.c \
+       getclose.c getdate.c gnats-pwconv.c gnatsd.c gnugetopt.c gnugetopt1.c \
+       index.c internal.c lists.c mail.c misc.c mk_auth.c pr-age.c \
+       pr-edit.c pr-init.c pr-stat.c pr.c query-pr.c query.c queue-pr.c \
+       regex.c version.c
>    make: don't know how to make send-pr. Stop
>    *** Error code 2
> I can get past this one by going into the send-pr directory and
> doing a "make" there. Next I get this error:
> -I . -o
> -I:No such file or directory
> *** Error code 1
> Stop in /usr/projects/tim/gnats-4.1.0.
> I manually ran "makeinfo -I . -o gnats.texi" from the
> doc directory to get around this.

Seems you using FreeBSD make instead of GNU make, so as ${MAKEINFO} has
been not substituted by its default value (makeinfo), and you unable to
built send-pr from top directory. Generally said, missing ".c.o"
expansions can be also done using GNU make.

Another question is why build process so unclean (missing .c files,
missing variables, some "magic" explicit rules at the end of makefile,
and so on)? IMHO we should cleanup makefiles to be compliant to generic
make rules or use GNU atomake framework (but I'm personally are not
familiar with GNU build tools). Which way more preferred?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]