Sam Steingold wrote:
if I remove the explicit call to gt_LC_MESSAGES
(which is called by AM_INTL_SUBDIR
which is called by AM_GNU_GETTEXT which we call explicitly)
then config.h.in no longer contains
#undef HAVE_LC_MESSAGES
why?
This is indeed unexpected. I believe it must be related to
On Wed, Jun 24, 2009 at 6:18 AM, Bruno Haiblebr...@clisp.org wrote:
Sam Steingold wrote:
if I remove the explicit call to gt_LC_MESSAGES
(which is called by AM_INTL_SUBDIR
which is called by AM_GNU_GETTEXT which we call explicitly)
then config.h.in no longer contains
#undef HAVE_LC_MESSAGES
Sam Steingold wrote:
The problem is triggered because you
have to invocations of gl_LIBSIGSEGV in a row, one from src/configure.in and
other one from the gnulib-generated gl_INIT macro. AC_LIB_LINKFLAGS was not
tested in this situation so far.
interesting!
so, you seem to imply that I
On Mon, Jun 22, 2009 at 4:31 AM, Bruno Haiblebr...@clisp.org wrote:
You can safely remove those gl_* macro invocations from configure.{ac,in}
for which you have explicitly requested the corresponding gnulib module -
because then it is guaranteed that gl_INIT will invoke that macro.
if I
Sam Steingold wrote:
I suspect it has something to do with the autoconf infrastructure of your
package. Can you provide a complete tarball of it? (The clisp cvs still has
libsigsegv.m4 serial 3.)
I reverted back to serial 3 so that my users can build.
try cvs up -D 2009-06-16
Tried
Sam Steingold wrote:
after:
$ grep -i sigsegv config.status
S[LIBSIGSEGV_PREFIX]=
S[LTLIBSIGSEGV]=
S[LIBSIGSEGV]=
S[HAVE_LIBSIGSEGV]=yes
D[HAVE_LIBSIGSEGV]= 1
D[HAVE_LIBSIGSEGV]= 1
...
$ ls -l /usr/include/sigsegv* /usr/lib*/libsigsegv*
8 -rw-r--r-- 1 root root 5802 Sep
On Thu, Jun 18, 2009 at 5:31 AM, Bruno Haiblebr...@clisp.org wrote:
Sam Steingold wrote:
after:
$ grep -i sigsegv config.status
S[LIBSIGSEGV_PREFIX]=
S[LTLIBSIGSEGV]=
S[LIBSIGSEGV]=
S[HAVE_LIBSIGSEGV]=yes
D[HAVE_LIBSIGSEGV]= 1
D[HAVE_LIBSIGSEGV]= 1
...
$ ls -l
On Mon, Jun 15, 2009 at 6:52 PM, Bruno Haiblebr...@clisp.org wrote:
Sam Steingold wrote:
I just upgraded clisp to libsigsegv.m4 serial 4
Did you do a make distclean; ./configure after doing so?
yes, of course.
and now LIBSIGSEGV is not set right:
config.status:
before:
$ grep -i
I just upgraded clisp to libsigsegv.m4 serial 4 and now LIBSIGSEGV is not set
right:
config.status:
before:
$ grep -i sigsegv config.status
S[LIBSIGSEGV]=-lsigsegv
S[LTLIBSIGSEGV]=-lsigsegv
D[HAVE_LIBSIGSEGV]= 1
D[HAVE_LIBSIGSEGV]= 1
after:
$ grep -i sigsegv config.status
Sam Steingold wrote:
I just upgraded clisp to libsigsegv.m4 serial 4
Did you do a make distclean; ./configure after doing so?
and now LIBSIGSEGV is not set right:
config.status:
before:
$ grep -i sigsegv config.status
S[LIBSIGSEGV]=-lsigsegv
S[LTLIBSIGSEGV]=-lsigsegv
10 matches
Mail list logo
