Problem with m4 in 2.3.6

Dennis J Perkins dperkins2 at
Mon Jul 24 18:59:14 PDT 2000

I had the same problem and my base system is also Debian.  I haven't tried again to
recompile it to use dynamic libraries due to a lack of time.

Panos Maheras wrote:

> I wrote:
> >> gcc  -o m4 m4.o builtin.o debug.o eval.o format.o freeze.o input.o macro.o
> >> output.o path.o stackovf.o symtab.o ../lib/libm4.a
> >> stackovf.o: In function `setup_stackovf_trap':
> >> /usr/src/m4-1.4/src/stackovf.c:343: the `sigstack' function is dangerous.
> >> `sigaltstack' should be used instead.
> John Phillips added:
> >A few of us get this problem (reason unknown).  My fix is to compile
> >m4 statically before the "chroot" and then re-compile properly after
> >autoconf and automake.
> This seems the only workable solution to the problem right now. Those 'few of
> us' happen by any chance to install LFS over a glibc 2.0 system (mine is Debian
> 2.1)?? After many *many* tests I'm beginning to think that it's a problem with
> glibc. Let me explain:



Mail archive:
IRC access: server: port: 6667 channel: #LFS
Unsubscribe: email lfs-discuss-request at and put
"unsubscribe" (without the quotation marks) in the body of the message
(no subject is required)

More information about the lfs-dev mailing list