Mailing List Archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Janusz wrote:
<<I have encountered some problems while building GPG 0.9.4, 0.9.5 and 0.9.6.
I'm using source of 0.4.5 with complete set of official patches up to 0.9.6.
They patch flawlesly then configure passes, but make throws up:

cd . && autoheader
/usr/bin/autoheader: Symbol ITH_SYMBOL_UNDERSCORE' is not covered by
/usr/lib/autoconf/acconfig.h ./acconfig.h
make: *** [stamp-h.in] Error 1>>

The precise same thing happened to me under identical circumstances.

<<My autoconf version is 2.12, automake is 1.3.>>

You need to upgrade your autoconf to 2.13. I was stumped by this
until I finally clued in and looked at a doc file and saw that they
changed the required autoconf to 2.13 on the sly.

Nate

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE3Of/68WKagKsEr/ERAr8zAKCGqt/B2rQzJ5NIts2gS9h4e29YiQCgj38d
rKaDaJw1sUBb7pRk6+lgL4E=
=qmvl
-----END PGP SIGNATURE-----

> Janusz wrote:
> <<I have encountered some problems while building GPG 0.9.4, 0.9.5 and 0.9.6.
> I'm using source of 0.4.5 with complete set of official patches up to 0.9.6.
> They patch flawlesly then configure passes, but make throws up:
>
> cd . && autoheader
> /usr/bin/autoheader: Symbol 'WITH_SYMBOL_UNDERSCORE' is not covered by
> /usr/lib/autoconf/acconfig.h ./acconfig.h
> make: *** [stamp-h.in] Error 1>>
>
> The precise same thing happened to me under identical circumstances.
>
> <<My autoconf version is 2.12, automake is 1.3.>>
>
> You need to upgrade your autoconf to 2.13. I was stumped by this
> until I finally clued in and looked at a doc file and saw that they
> changed the required autoconf to 2.13 on the sly.

It worked. Thank you. So, why doesn't configure detect older autoconf and
report this ? This is, like a bug.
Alex
--
* | Janusz A. "Alex" Urbanowicz, \ Home: <alex@bofh.torun.pl>
--+~| | http://eris.phys.uni.torun.pl/~alex/ \ Work: <alex@bofh.net.pl>
`_|/ | "Historii nie mo¿na tworzyæ. \____ RSA: 512/0xAB425659
| | Mo¿na jedynie mieæ nadziejê, ¿e siê j± przetrwa." - G'Kar, Babylon 5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex wrote:
<<It worked. Thank you. So, why doesn't configure detect older autoconf and
report this ? This is, like a bug.>>

That's be nice, would it? I think this is probably an
autoconf problem, not a GPG problem. The required version
*was* specified in the docs, yet it's a pain when you
upgrade and only get a cryptic build error. GPG isn't
the only package with this problem. I've had the same
deal, say, upgrading the Linux kernel and finding that
ppp was broken until I upgraded pppd.

Nate
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE3PXAw8WKagKsEr/ERApsVAJ9hRkiOWppnzO0qitfhF37RzqUugwCgoKiJ
VIuv0VrJivrlgNduV+x+Qgs=
=i8HI
-----END PGP SIGNATURE-----

On Thu, 13 May 1999, Janusz A. Urbanowicz wrote:
> It worked. Thank you. So, why doesn't configure detect older autoconf and
> report this ? This is, like a bug.

Easily fixed with the addition of the following line to configure.in:

AC_PREREQ(2.13)

--
Edward S. Marshall <emarshal@logic.net> [ What goes up, must come down. ]
http://www.logic.net/~emarshal/ [ Ask any system administrator. ]

Linux labyrinth 2.3.0 #1 Wed May 12 09:22:19 CDT 1999 i586 unknown
10:05am up 2 days, 14:01, 4 users, load average: 0.33, 0.12, 0.03