Problem with m4 in 2.3.6

Gerard Beekmans gerard at
Mon Jul 24 07:06:53 PDT 2000

> If this turns out to be a glibc 2.0 problem *maybe* we should follow what John
> Phillips suggested: compile statically before and dynamically after (this seems
> to work right now).

Have you confirmed this? If M4 is included in the static section, can it
be compilede ok in the dynamic one? Somehow I doubt it. I don't see how
a static M4 would fix these header problems. Even if M4 is static, you
still will have that sigalstack (or whatever it's called) problem after
you have chroot'ed.

Gerard Beekmans

-*- If Linux doesn't have the solution, you have the wrong problem -*-
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