On 2014-05-01, at 23:46, Edward Kmett ekm...@gmail.com wrote:
With the old custom linker we weren't able to get our custom MPFR linked in
properly on all platforms for use in ghci.
On Macs we ran into some rather interesting problems. We could get it to
work for actual executables, but ghci
On 07/05/2014 05:11, Dominick Samperi wrote:
OK, so if I understand correctly, there is no point trying to
narrow down my issue further as it is not supposed to work
with DYNAMIC_GHC_PROGRAMS=NO (because this disables
use of the system linker).
On the contrary, if the external C++ code that
OK, so if I understand correctly, there is no point trying to
narrow down my issue further as it is not supposed to work
with DYNAMIC_GHC_PROGRAMS=NO (because this disables
use of the system linker). Furthermore, if the plan to disable
some form of GHC dynamic linkage is carried out, this should
no, i was saying LLVM-General when static linked to llvm doesnt work. I
wasnt talking about ghc being dynamic or static
merely that theres no way to get llvm-general to work on ghci in 7.6 afaik
On Mon, May 5, 2014 at 4:54 PM, Simon Marlow marlo...@gmail.com wrote:
I don't see any reason why
On 03/05/14 04:15, Dominick Samperi wrote:
I'm trying to understand the dynamic linking situation with the help of
https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8, and according
to this information I need to specify DYNAMIC_GHC_PROGRAMS=YES
for ghci to use the system linker. I don't
On 05/05/14 21:58, Carter Schonwald wrote:
no, i was saying LLVM-General when static linked to llvm doesnt work. I
wasnt talking about ghc being dynamic or static
I believe you that it doesn't work. But I think that if you use a
dynamically-linked llvm (i.e. the shared-llvm flag), it
I think the issue is really loading static C++ libs into GHCi doesn't
work properly, and that's true of all versions of GHC, including 7.8.
On 05/05/14 22:08, Carter Schonwald wrote:
i don't have 7.6 setup anymore, i'll see about reproducing the issue
later. it falls under the umbrella of
The problems I was seeing with ghci prior to 7.8 are similar to the
ones reported by Edward Kmett above: addresses were mapped
incorrectly. This was compounded by the fact that the
library used was not thread-safe, so there were two issues,
which may explain why -fno-ghci-sandbox did not help.
On
On 02/05/2014 14:28, Edward Kmett wrote:
Perhaps. We actually tried that originally, but had issues about
where and how to get cabal to place it. We'd need it to go somewhere
installed rather than the local build dir lest it not be there when
we go to use the lib, but IIRC, cabal
I may have to dig to find an example, but when I last checked it seemed
that c++ libraries would load fine, but there was a problem with static
initializers not getting called, when loading from ghci, so if your c++
library needed them then you'd have problems.
An earlier version of the MPFR
I downloaded HEAD and placed DYNAMIC_GHC_PROGRAMS=NO in the quick
section of mk/build.mk (with BuildFlavour = quick), and set
DYNAMIC_GHC_PROGRAMS=NO
in my environment before running configure (just to be sure!). Near
the end of the build
I saw some messages like Warning: vectorization failure,
On May 2, 2014, at 9:05 AM, Simon Marlow marlo...@gmail.com wrote:
On 02/05/2014 00:46, Edward Kmett wrote:
With the old custom linker we weren't able to get our custom MPFR linked
in properly on all platforms for use in ghci.
On Macs we ran into some rather interesting problems. We
On Fri, May 2, 2014 at 10:19 AM, Edward Kmett ekm...@gmail.com wrote:
I may have to dig to find an example, but when I last checked it seemed
that c++ libraries would load fine, but there was a problem with static
initializers not getting called, when loading from ghci, so if your c++
library
On 02/05/14 18:19, Edward Kmett wrote:
I may have to dig to find an example, but when I last checked it seemed
that c++ libraries would load fine, but there was a problem with static
initializers not getting called, when loading from ghci, so if your c++
library needed them then you'd have
Can you give me a quick summary of how to reproduce the problem? (not
including the GHC build steps)
Cheers,
Simon
On 02/05/14 18:18, Dominick Samperi wrote:
I downloaded HEAD and placed DYNAMIC_GHC_PROGRAMS=NO in the quick
section of mk/build.mk (with BuildFlavour = quick), and set
On 02/05/2014 01:09, Dominick Samperi wrote:
If I understand your last comment correctly linking to libR should
continue to work, even if you revert to static linking of Haskell compiled
code via RTS linker. Since you say this is the way things have always
been, perhaps the real explanation for
On 02/05/2014 00:46, Edward Kmett wrote:
With the old custom linker we weren't able to get our custom MPFR linked
in properly on all platforms for use in ghci.
On Macs we ran into some rather interesting problems. We could get it to
work for actual executables, but ghci would segfault with
| Dynamic linking has been a huge headache in GHC, and it's not clear that
| it's an overall improvement compared with the static linker. Now that
| 7.8 is out of the way, it's time to have a conversation about whether we
| want to do dynamic linking again for 7.10, or revert to static linking.
On 01/05/2014 02:26, George Colpitts wrote:
To elaborate, in the past, I had a lot of problems using libraries from
the ghci prompt on the Mac but I haven't tried recently.
As an example, on the web page
http://www.cs.yale.edu/homes/hudak/SOE/software1.htm for the book the
Haskell School of
On 01/05/14 14:48, Dominick Samperi wrote:
The problem with some graphics libraries used via FFI (and other libraries
that are not thread-safe), if I understand the situation correctly, is that ghci
forks a thread when it shouldn't, causing some programs to miscalculate
the available stack space
On Thu, May 1, 2014 at 5:30 PM, Simon Marlow marlo...@gmail.com wrote:
We should fix this (or at least make it a lot less likely). Is there a
ticket?
Not yet. I just converted to 7.8.2 the other day (I'd been running the
release candidate) and wanted to duplicate the problem first. I haven't
It turns out that the 7.8 update fixed problems that were NOT
fixed by using -fno-ghci-sandbox with earlier versions of ghci,
like 7.6.3, so this flag by itself did not address the issue. I
assumed (perhaps incorrectly) that a full explanation must
include the new dynamic linking support.
With
Done now.
OK, unless anyone has anything else major going in, I'll look for
typos closely and send it to Mihail later today.
It filled up pretty fast - thanks for the haste everyone!
On Tue, Apr 29, 2014 at 7:46 PM, Austin Seipp aus...@well-typed.com wrote:
Good idea! Definitely one of the
Added a few sentences about DWARF support - we should really aim to get
this done for 7.10.
Greetings,
Peter Wortmann
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
Great, thanks Peter!
On Wed, Apr 30, 2014 at 8:29 AM, Peter Wortmann sc...@leeds.ac.uk wrote:
Added a few sentences about DWARF support - we should really aim to get
this done for 7.10.
Greetings,
Peter Wortmann
___
ghc-devs mailing list
On 30/04/2014 01:35, George Colpitts wrote:
It doesn't have anything about the dynamic linking changes made for 7.8.
I think it's worth mentioning the improvements we expect to get from
that. The highlights of the release notes do mention it, so maybe that
suffices.
In particular, I'm hoping
Hi,
On Wed, 30 Apr 2014 17:45:35 +0100, Simon Marlow marlo...@gmail.com writes:
Dynamic linking has been a huge headache in GHC, and it's not clear
that it's an overall improvement compared with the static linker. Now
that 7.8 is out of the way, it's time to have a conversation about
To elaborate, in the past, I had a lot of problems using libraries from the
ghci prompt on the Mac but I haven't tried recently.
As an example, on the web
pagehttp://www.cs.yale.edu/homes/hudak/SOE/software1.htmfor the book
the Haskell School of Expression it says:
Note for OS X users: running
Good idea! Definitely one of the biggest changes.
On Tue, Apr 29, 2014 at 7:35 PM, George Colpitts
george.colpi...@gmail.com wrote:
It doesn't have anything about the dynamic linking changes made for 7.8. I
think it's worth mentioning the improvements we expect to get from that. The
highlights
29 matches
Mail list logo
