configure m4 problem

Ozkan Sezer sezeroz at
Thu Aug 19 00:43:43 CEST 2010

On Wed, Aug 18, 2010 at 11:11 AM, Niels Möller <nisse at> wrote:
> Ozkan Sezer <sezeroz at> writes:
> I'm not sure I understand what happens.
> Can you explain how the M4 variable in GMPs configure script propagates
> to the configuration of gcc? As a shell variable (I don't even know if
> configure variables like this are supposed to be exported), or via
> substitution in some Makefile, or via config.cache, or...
> I understand neither the reason for the current behaviour, nor the
> details of the problem it causes.
> Regards,
> /Niels

This is what I got from our builders / configury maintainers:

"The configure script is running flex using a nonexistent M4.
That causes a sigpipe, which leaves a useless orphaned file.
The configure script looks at that and says "ok, flex works".
Under python, sigpipe gets filtered out.  So, flex cleans up
after itself (as it should), thus deleting the file, and so
the configure script thinks flex is broken (when in reality,
the configure script is wrong and flex reported correctly.)
M4 can't be defined before running AM_PROG_LEX, and it should
not be defined al all in that fashion, either."

I hope this clears things?



More information about the gmp-devel mailing list