public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Bug? LLVM builds fail on 1.7.8 (fenv.h)
@ 2011-03-09 16:54 Magnus Reftel
  2011-03-10  9:32 ` Corinna Vinschen
  0 siblings, 1 reply; 5+ messages in thread
From: Magnus Reftel @ 2011-03-09 16:54 UTC (permalink / raw)
  To: cygwin

Hi all,

it seems that the fenv.h introduction may have caused some problems.
LLVM fails to build now, and fit seems to me that it could be because
#define _GLIBCXX_HAVE_FENV_H 1
is missing in
/usr/lib/gcc/i686-pc-cygwin/4.3.4/include/c++/i686-pc-cygwin/bits/c++config.h

For the analysis, please see LLVM bug 9436 at
http://llvm.org/bugs/show_bug.cgi?id=9436

BR
Magnus Reftel

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug? LLVM builds fail on 1.7.8 (fenv.h)
  2011-03-09 16:54 Bug? LLVM builds fail on 1.7.8 (fenv.h) Magnus Reftel
@ 2011-03-10  9:32 ` Corinna Vinschen
  2011-03-10  9:59   ` Corinna Vinschen
  0 siblings, 1 reply; 5+ messages in thread
From: Corinna Vinschen @ 2011-03-10  9:32 UTC (permalink / raw)
  To: cygwin

On Mar  9 17:47, Magnus Reftel wrote:
> Hi all,
> 
> it seems that the fenv.h introduction may have caused some problems.
> LLVM fails to build now, and fit seems to me that it could be because
> #define _GLIBCXX_HAVE_FENV_H 1
> is missing in
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/include/c++/i686-pc-cygwin/bits/c++config.h
> 
> For the analysis, please see LLVM bug 9436 at
> http://llvm.org/bugs/show_bug.cgi?id=9436

This isn't a Cygwin bug, but a bug in LLVM.

How on earth can anybody expect that a define _GLIBCXX_HAVE_FENV_H is
set on a system which doesn't even *use* glibc?

The right thing to do for LLVM would be to add a autoconf test to
check for fenv.h and then use HAVE_FENV_H instead of realying on a
system-dependent define in one of the compiler headers.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug? LLVM builds fail on 1.7.8 (fenv.h)
  2011-03-10  9:32 ` Corinna Vinschen
@ 2011-03-10  9:59   ` Corinna Vinschen
  2011-03-10 10:16     ` Yaakov (Cygwin/X)
  0 siblings, 1 reply; 5+ messages in thread
From: Corinna Vinschen @ 2011-03-10  9:59 UTC (permalink / raw)
  To: cygwin

On Mar 10 10:26, Corinna Vinschen wrote:
> On Mar  9 17:47, Magnus Reftel wrote:
> > Hi all,
> > 
> > it seems that the fenv.h introduction may have caused some problems.
> > LLVM fails to build now, and fit seems to me that it could be because
> > #define _GLIBCXX_HAVE_FENV_H 1
> > is missing in
> > /usr/lib/gcc/i686-pc-cygwin/4.3.4/include/c++/i686-pc-cygwin/bits/c++config.h
> > 
> > For the analysis, please see LLVM bug 9436 at
> > http://llvm.org/bugs/show_bug.cgi?id=9436
> 
> This isn't a Cygwin bug, but a bug in LLVM.
> 
> How on earth can anybody expect that a define _GLIBCXX_HAVE_FENV_H is
> set on a system which doesn't even *use* glibc?
> 
> The right thing to do for LLVM would be to add a autoconf test to
> check for fenv.h and then use HAVE_FENV_H instead of realying on a
> system-dependent define in one of the compiler headers.

Hang on, I take that back.  I just realized that this is actually all
in the GCC header files and that GCC actually uses _GLIBC prefixed
macros, even on systems not using glibc.  Oh well.

Dave?  Any chance we can get a new gcc 4.3.4 package with this change
ASAP?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug? LLVM builds fail on 1.7.8 (fenv.h)
  2011-03-10  9:59   ` Corinna Vinschen
@ 2011-03-10 10:16     ` Yaakov (Cygwin/X)
  2011-03-10 11:43       ` Corinna Vinschen
  0 siblings, 1 reply; 5+ messages in thread
From: Yaakov (Cygwin/X) @ 2011-03-10 10:16 UTC (permalink / raw)
  To: cygwin

On Thu, 2011-03-10 at 10:31 +0100, Corinna Vinschen wrote:
> \Hang on, I take that back.  I just realized that this is actually all
> in the GCC header files and that GCC actually uses _GLIBC prefixed
> macros, even on systems not using glibc.  Oh well.
> 
> Dave?  Any chance we can get a new gcc 4.3.4 package with this change
> ASAP?

From a previous discussion with Dave, that should be a 4.5.2 built
against 1.7.8.  If that's not happening really soon, though, I'll
probably spin a release for Ports instead.


Yaakov



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug? LLVM builds fail on 1.7.8 (fenv.h)
  2011-03-10 10:16     ` Yaakov (Cygwin/X)
@ 2011-03-10 11:43       ` Corinna Vinschen
  0 siblings, 0 replies; 5+ messages in thread
From: Corinna Vinschen @ 2011-03-10 11:43 UTC (permalink / raw)
  To: cygwin

On Mar 10 03:59, Yaakov (Cygwin/X) wrote:
> On Thu, 2011-03-10 at 10:31 +0100, Corinna Vinschen wrote:
> > \Hang on, I take that back.  I just realized that this is actually all
> > in the GCC header files and that GCC actually uses _GLIBC prefixed
> > macros, even on systems not using glibc.  Oh well.
> > 
> > Dave?  Any chance we can get a new gcc 4.3.4 package with this change
> > ASAP?
> 
> >From a previous discussion with Dave, that should be a 4.5.2 built
> against 1.7.8.  If that's not happening really soon, though, I'll
> probably spin a release for Ports instead.

IIUC fenv does not rely on 4.5.x, it's just that 4.5.x needs fenv,
isn't it?

So, for the time being it should be sufficient to get a gcc4-g++-4.3.3-4
package with just a tweaked c++config.h.  I have often replaced a file
in a package by just unpacking and repacking the source and binary
packages without rebuilding, but I don't know if this c++config.h change
would require a rebuild...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-03-10 10:16 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-09 16:54 Bug? LLVM builds fail on 1.7.8 (fenv.h) Magnus Reftel
2011-03-10  9:32 ` Corinna Vinschen
2011-03-10  9:59   ` Corinna Vinschen
2011-03-10 10:16     ` Yaakov (Cygwin/X)
2011-03-10 11:43       ` Corinna Vinschen

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).