On Tue, Dec 19, 2006 at 09:31:30PM -0500, Bruce Walker wrote:
> Bruce Walker wrote:
> >I've been copying in missing bits from the libevent-1.2a.tar.gz
> >tarball and it almost builds. I'm stuck at,
> >
> >/usr/local/bin/bash ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I.
> >-I. -I. -Icompat -O -pipe -g -O2 -Wall -c -o event.lo `test -f
> >'event.c' || echo './'`event.c
> >libtool: compile: unable to infer tagged configuration
> >libtool: compile: specify a tag with `--tag'
> >*** Error code 1
>
> Ok, turns out that *that* error was caused by me copying in files that
> had been configured in the ports tree on a FreeBSD 6.1 system to my
> compile box running FreeBSD 4.10. Fixed by copying files from the 4.10
> ports tree. D'oh!
>
> But I'm still mystified by the lack of configure files in the svn tree.
> I'd still be interested in the 10-cent tour of that.
Many (most?) projects don't commit a configure script. The configure script
is generated from configure.ac (or previously configure.in). Arguably you
don't want to commit generated code, only the source.
Typically, the configure scripts (and other odds and ends) are attended to
while creating a release tarball. To generate it yourself, you would do
something like this from the source directory:
aclocal
autoheader
automake
autoconf
Or something like that.
GNU Autotools is notoriously difficult to wield, not the least because each
independent revision of the various tools mentioned above creates
intolerable incompatibilities with every other version. It quickly becomes
something of a dark art (for the blessed few) or more typically an excercise
in self-immolation.
And that's coming from somebody who actually uses and appreciates M4, the
macro language/parser which is employed heavily by autotools because it's one
of the few dependable utilities common and compatible amongst all Unix
platforms.
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo/libevent-users
