From: Jay <jayk123@hotmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Andrew Pinski <pinskia@gmail.com>, <gcc@gcc.gnu.org>
Subject: RE: configuring in-tree gmp/mpfr with "none"?
Date: Mon, 04 Aug 2008 10:26:00 -0000 [thread overview]
Message-ID: <COL101-W39765618E56F15427E078FE6780@phx.gbl> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2008-08-04 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 16:50 Jay
2008-06-17 17:40 ` Andrew Pinski
2008-06-18 4:54 ` Jay
[not found] ` <BAY139-W155015ADB5180EDEAB8B9CE6AB0@phx.gbl>
2008-06-18 10:54 ` Andrew Pinski
2008-07-31 11:45 ` Jay
2008-07-31 15:00 ` Paolo Bonzini
2008-08-04 10:26 ` Jay [this message]
2008-08-04 11:06 ` Paolo Bonzini
2008-08-04 14:47 ` Vincent Lefevre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=COL101-W39765618E56F15427E078FE6780@phx.gbl \
--to=jayk123@hotmail.com \
--cc=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).