Re: libsigsegv questions

[Eric Blake]

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

According to Bruno Haible on 6/4/2008 2:40 PM:
| The homepages
|   http://www.gnu.org/software/libsigsegv/
|   http://libsigsegv.sourceforge.net/
| mention two email addresses; these email addresses occur also in the AUTHORS
| file and in the ChangeLog file, so that's where most people write. Anyway,
| one of the two addresses that you picked was right :-)

I'm just a bit surprised that you are favoring a personal, non-archived
mail over a list address.  Even just setting up bug-libsigsegv to forward
to bug-gnu-utils (similar to your bug-gettext forwarder) would be a nice
gesture :)  At any rate, would you welcome a patch to use the more modern
AC_INIT invocation, and if so, which bug reporting address would it use?

| The sources available at the location mentioned in
|   http://savannah.gnu.org/cvs/?group=libsigsegv
| Yes, it's only CVS.

Fair enough.  Let me know if you'd like help converting it to git.

|
|> I'm considering using libsigsegv in m4, and I'm debating about including
|> libsigsegv as a subpackage rather than requiring it as an externally
|> installed dependency.
|
| I would recommend to use it only as an external dependency. The reason
is that
| libsigsgev sometimes sees rapid new releases due to new platforms. (A new
| release for 64-bit MacOS X is pending, for example.) If you include the
| library in your package, it's not so easy for the users of your package to
| use the newest libsigsegv version.

Good arguments.  When I get around to dumping m4's own stackovf.c and
replacing it with libsigsegv when available, and gnulib's c-stack when the
external library is not present, I will stick with the external dependency
(and not distribute libsigsegv as a subproject).

|
| For your information, attached you find the libsigsegv detection macro from
| GNU clisp.

That used AC_LIB_PREPARE_PREFIX, AC_LIB_RPATH, AC_LIB_LINKFLAGS_BODY, and
AC_LIB_APPENDTOVAR, all in the autoconf namespace, but none of them
provided by autoconf (yet).  Where are they defined, and are they worth
pushing into autoconf proper (for 2.63 or later) as useful macros?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhHSOAACgkQ84KuGfSFAYCrhwCgp6NJUhuBZsAkS8xDERq+JUGD
OXgAn3mE+GJMlzJJk8tBfmc1KFwqfvZP
=vLlC
-----END PGP SIGNATURE-----