#3935: buggy libffi
---------------------------------+------------------------------------------
    Reporter:  guest             |        Owner:                     
        Type:  bug               |       Status:  new                
    Priority:  normal            |    Milestone:                     
   Component:  Compiler          |      Version:  6.13               
    Keywords:                    |   Difficulty:                     
          Os:  Unknown/Multiple  |     Testcase:                     
Architecture:  Unknown/Multiple  |      Failure:  Building GHC failed
---------------------------------+------------------------------------------
Description changed by igloo:

Old description:

> The version of libffi in use in the current builds has a bug in it which
> cauzes the build to fail on the nightly snapshots
> (ghc-6.13.20100320-src.tar.bz2 etc)
>
> and on the STABLE package in darcs.haskell.org (atleast it did here).
>
> In src/x86/ffi.c
>
> line 136-137 should be
>
>     case FFI_TYPE_DOUBLE:
> #ifdef HAVE_LONG_DOUBLE
>     case FFI_TYPE_LONGDOUBLE:
> #endif
>
> instead of
>
>     case FFI_TYPE_DOUBLE:
>     case FFI_TYPE_LONGDOUBLE:
>
> updating to libffi-0.3.9 should fix this.

New description:

 The version of libffi in use in the current builds has a bug in it which
 cauzes the build to fail on the nightly snapshots
 (ghc-6.13.20100320-src.tar.bz2 etc)

 and on the STABLE package in darcs.haskell.org (atleast it did here).

 In src/x86/ffi.c

 line 136-137 should be
 {{{
     case FFI_TYPE_DOUBLE:
 #ifdef HAVE_LONG_DOUBLE
     case FFI_TYPE_LONGDOUBLE:
 #endif
 }}}
 instead of
 {{{
     case FFI_TYPE_DOUBLE:
     case FFI_TYPE_LONGDOUBLE:
 }}}
 updating to libffi-0.3.9 should fix this.

--

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3935#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to