Re: Call for features for GHC 8.4

2017-10-09 Thread Ben Gamari
Evan Laforge  writes:

> I'd like to see this fixed: https://ghc.haskell.org/trac/ghc/ticket/13604
>
> It's a show stopper that prevented me from being able to use 8.2 at all.

David, could you see to it that something happens on this front?

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


Re: Call for features for GHC 8.4

2017-10-09 Thread Evan Laforge
I'd like to see this fixed: https://ghc.haskell.org/trac/ghc/ticket/13604

It's a show stopper that prevented me from being able to use 8.2 at all.

Once again, if no one has time to address it, I'd be happy to take a
look myself.

On Mon, Oct 9, 2017 at 9:15 AM, Ben Gamari  wrote:
> Hello everyone,
>
> The release of GHC 8.4 is quickly approaching, with a release targetted
> for February 2018. To allow plenty of time for stabilization, we would
> like to cut the ghc-8.4 branch sometime in November. Currently there are
> relatively few items on the 8.4 status page [1]. If you have a feature
> which you would like to see in 8.4 but is not listed there please do
> add it soon.
>
> Also note that if things go according to plan, 8.6 will come a mere six
> months after 8.4 so if you have a large feature which won't make it for
> 8.4, do not fret; another release will be just around the corner.
>
> Cheers,
>
> - Ben
>
>
> [1] https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-8.4.1
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


Call for features for GHC 8.4

2017-10-09 Thread Ben Gamari
Hello everyone,

The release of GHC 8.4 is quickly approaching, with a release targetted
for February 2018. To allow plenty of time for stabilization, we would
like to cut the ghc-8.4 branch sometime in November. Currently there are
relatively few items on the 8.4 status page [1]. If you have a feature
which you would like to see in 8.4 but is not listed there please do
add it soon.

Also note that if things go according to plan, 8.6 will come a mere six
months after 8.4 so if you have a large feature which won't make it for
8.4, do not fret; another release will be just around the corner.

Cheers,

- Ben


[1] https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-8.4.1


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


Re: GHC HEAD now needs extra tools to build libffi?

2017-10-09 Thread Moritz Angermann
Yes, this commit indeed introduced the need for makeinfo, however after some 
debugging and improved packaging of the external libffi library, this 
dependency was removed again, and should not be required with the latest head 
anymore.

Then again this should not result in link issues but rather in build time 
issues.

The key to libffi is the libffi-tarballs git submodule, which contains the 
packaged libffi-tarballs. Make sure all your submodules are also updated.

I usually use `git -x -f -d` (read the documentation first) to ensure a clean 
working tree. Especially as you say you can’t reproduce it on other machines, 
maybe there is a file in your tree that the cleaning did not catch?

Sent from my iPhone

> On 9 Oct 2017, at 4:31 AM, Thomas Jakway  wrote:
> 
> I'm on Ubuntu 16.10.
> 
> I ran git bisect:
> 
> --
> 
> e515c7f37be97e1c2ccc497ddd0a730e63ddfa82 is the first bad commit
> commit e515c7f37be97e1c2ccc497ddd0a730e63ddfa82
> Author: Moritz Angermann 
> Date:   Sat Sep 30 09:31:12 2017 -0400
> 
> Allow libffi snapshots
> 
> This is rather annoying. I'd prefer to have a stable release to
> use. However libffi-3.2.1 has been released November 12, 2014, and
> libffi-4 is TBD. See also https://github.com/libffi/libffi/issues/296
> 
> The core reason for this change is that llvm changed the supported
> assembly to unified syntax, which libffi-3.2.1 does not use, and hence
> fails to compile for arm with llvm. For refence, see the following
> issue: https://github.com/libffi/libffi/issues/191.
> 
> This diff contains a script to generate a tarball for the
> `libffi-tarballs` repository from the libffi GitHub repository; as well
> as the necessary changes to the build system.
> 
> Updates libffi-tarballs submodule.
> 
> Reviewers: austin, bgamari, hvr
> 
> Subscribers: hvr, erikd, rwbarton, thomie
> 
> Differential Revision: https://phabricator.haskell.org/D3574
> 
> --
> 
> I can't reproduce it on my other linux computers though.
> 
> 
>> On 10/04/2017 02:17 PM, Ben Gamari wrote:
>> Thomas Jakway  writes:
>> 
>>> Anyone else getting linker errors?
>>> 
>>> This is after running
>>> 
>>> make clean && make distclean && find . -name "*.o" -type f -delete &&
>>> find . -name "*.hi" -type f -delete
>>> 
>>> then
>>> 
>>> ./boot && ./configure && make -j5
>>> 
>>> (ghc-new is not a new checkout, this error is happening on a branch I'm
>>> working on, but one that doesn't touch the FFI)
>>> 
>> I'm afraid I can't reproduce this. What platform/operating system is
>> this on?
>> 
>> Cheers,
>> 
>> - Ben
> 
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs