This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: configuring in-tree gmp/mpfr with "none"?
- From: Jay <jayk123 at hotmail dot com>
- To: Paolo Bonzini <bonzini at gnu dot org>
- Cc: Andrew Pinski <pinskia at gmail dot com>, <gcc at gcc dot gnu dot org>
- Date: Mon, 4 Aug 2008 10:25:18 +0000
- Subject: RE: configuring in-tree gmp/mpfr with "none"?
- References: <BAY139-W162C29DAF463FFF6ABB94FE6AE0@phx.gbl> <de8d50360806171039g13d89b36necbc8a67b853e278@mail.gmail.com> <BAY139-W155015ADB5180EDEAB8B9CE6AB0@phx.gbl> <de8d50360806180353x64578a63y20508f5841efd1f@mail.gmail.com> <COL101-W53CA343E1A70D50CEF70C1E67C0@phx.gbl> <4891C3E7.4050401@gnu.org>
> Because at some point, no released version worked on intel macs.
Long since passed and can be removed?
Or only do it on those machines??
Granted, the Python-wrapping-build I'm doing ought to work as well on Intel Macs as anywhere else.
Here is what ends up happening:
#include
#include
int main()
{
signal(SIGPIPE, SIG_IGN); << Python does like this
putenv("M4=foo"); << gmp/configure does like this
system("flex 1.l"); << gmp/configure does like this
return 0;
}
Without ignoring sigpipe, flex dies in filter_tee_header reading the output of a failed exec.
Ignoring the signal under a Python wrapper however, it continues on
and deletes the output, causing gmp/configure to fail because it is looking
for the output.
gmp/configure is where the blame really lies, but if gcc configured gmp "normally",
this wouldn't occur. Or, is cpu=none not so abnormal? Just that I hadn't seen it?
(Everything new and normal is initially new and abnormal, of course.)
- Jay
> Date: Thu, 31 Jul 2008 15:53:43 +0200
> From: bonzini@gnu.org
> To: jayk123@hotmail.com
> CC: pinskia@gmail.com; gcc@gcc.gnu.org
> Subject: Re: configuring in-tree gmp/mpfr with "none"?
>
> Jay wrote:
>> Andrew, Can you explain more why?
>
> Because at some point, no released version worked on intel macs.
>
>> And then gmp/configure runs flex.
>> And then sometimes?always flex tries to run getenv("M4") || "m4".
>
> Yes, Flex uses m4.
>
>> gmp/configure probably should not be setting M4
>
> Yes, I think that setting M4=m4-not-needed should be done only for
> debugging purposes. Otherwise, GMP should always look for m4 in its
> configure script, and set it to a valid value in the makefile.
>
> Paolo