Hi Mark,
Thank you for the clarification.
I think, then, that we should indeed provide a link to a notice about
native libraries - like, "if you're using native libraries, make sure
their architecture is 32-bit or universal as well; in case of
MacPorts you can achieve this by doing port install
I've filed a bug report: http://hackage.haskell.org/trac/ghc/ticket/7314
My only problem is that I don't have OS X 10.8 installed on my machine.
I'm running OS X 10.6, and am not inclined to upgrade.
So providing feedback on the questions related to the bug report will be hard
and/or take some ti
I'm the source of the 32-bit recommendation, and the HP Mac distribution
builder
To summarize what I read in this thread:
1. 32-bit GHC/HP didn't work with 64-bit Cario libs
2. Some libs available via brew were 64-bit, and 32-bit ones would have
to be compiled
3. There is still some b
Eugene: I think thats a bug / ticket for the haskell platform trac, rather
than ghc's trac.
look forward to seeing how to reproduce those problems / helping fix em!
On Mon, Oct 8, 2012 at 3:08 PM, Eugene Kirpichov wrote:
> Johan, should I also file the bugreport "remove the suggestion to
> insta
Johan, should I also file the bugreport "remove the suggestion to
install 32-bit platform" there, or is there a different place for bugs
of the platform website?
On Mon, Oct 8, 2012 at 7:25 AM, Johan Tibell wrote:
> On Mon, Oct 8, 2012 at 3:28 AM, Christiaan Baaij
> wrote:
>> Hi,
>>
>> I finally
On Mon, Oct 8, 2012 at 3:28 AM, Christiaan Baaij
wrote:
> Hi,
>
> I finally found another OS X mountain lion install and can confirm the
> behaviour I described earlier:
> 32-bit: compiled code works, interpreted code works
> 64-bit: compiled code works, interpreted code fails
>
> Here's the test
On Monday, 8 October 2012 at 06:28, Christiaan Baaij wrote:
> ghci: segfault
> ghci from gdb: everything works
This makes me suspect something that gets disabled when debugging, such as
address space randomization and the like. I did not think ML handled that any
differently from Lion, though.
Hi,
I finally found another OS X mountain lion install and can confirm the
behaviour I described earlier:
32-bit: compiled code works, interpreted code works
64-bit: compiled code works, interpreted code fails
Here's the test case:
- cabal install gloss --flags"-GLUT GLFW"
- cabal unpack gloss-e
The GLUT-backend calls system.exit when the window is closed, because
'exitMainLoop' is only defined within freeglut, which is not by default
installed on non-linux platforms.
There is hence no real point in running gloss applications with the
GLUT-backend from GHCi.
I'll try to find a mountain
Carter:
Not yet.
I'll get round to it once I'm done with with an Agda presentation I'm
working on. Until then I can't afford to break my environment.
On Fri, Sep 28, 2012 at 1:56 PM, Carter Schonwald
wrote:
> do these problems also happen if your'e using the glut backend? (because if
> its only
do these problems also happen if your'e using the glut backend? (because if
its only glfw that has problems, then its something wrong in the ffi code,
but if its both, that suggests there may be some sort of systematic
problem?)
@Lyndon, that sounds like a bug... especially since scotty seems to h
I'm experiencing the same issues with compiled 64 bit working
correctly, but interpreted causing all sorts of issues with Scotty.
On Thu, Sep 27, 2012 at 3:45 PM, Christiaan Baaij
wrote:
> The behaviour seems to differ between versions of OS X.
>
> A student has OS X 10.8 installed and is observi
The behaviour seems to differ between versions of OS X.
A student has OS X 10.8 installed and is observing the described behaviour:
32-bit: interpreted and compiled work correctly
64-bit: only compiled code works correctly
However, I have OS X 10.6, and I'm observing the following behaviour:
32-b
really? does the 64 bit code work correctly when compiled?
if the compiled version works correctly, could you post a repo of some
example codlets that *should work* on ghc 7.6 so i can sort out if its
fixable. There were some similar problems with gtk / cairo for a while on
OS X, and i was able t
Running gloss [1] programs from GHCi only works with the 32bit version of the
latest Haskell Platform.
The 64-bit version just shows a black window and GHCi becomes unresponsive.
I use gloss to display trees and graphs in the functional programming course
given at our university.
The ability to
Adding Mark who's the release manager for the platform (and also the
maintainer of the OS X builds).
On Wed, Sep 26, 2012 at 11:57 AM, Erik Hesselink wrote:
> On Wed, Sep 26, 2012 at 10:58 AM, Johan Tibell wrote:
>> On Wed, Sep 26, 2012 at 7:44 AM, Carter Schonwald
>> wrote:
>>> To the best of
On 2012-09-26, at 1:44 AM, Carter Schonwald wrote:
> what can we (the community ) do to address the fact that the haskell platform
> installer suggestions for os x are sadly completely backwards? (or am I
> completely wrong in my personal stance on this matter)
>
I'd much prefer the 64 bit m
On Wed, Sep 26, 2012 at 10:58 AM, Johan Tibell wrote:
> On Wed, Sep 26, 2012 at 7:44 AM, Carter Schonwald
> wrote:
>> To the best of my knowledge there is absolutely no reason to use the 32bit
>> haskell on OS X (aside from memory usage optimization cases which likely do
>> not matter to the *typ
Hi,
On Wed, Sep 26, 2012 at 7:44 AM, Carter Schonwald
wrote:
> To the best of my knowledge there is absolutely no reason to use the 32bit
> haskell on OS X (aside from memory usage optimization cases which likely do
> not matter to the *typical* user), and the community should probably update
> t
Hi Eugene,
To the best of my knowledge there is absolutely no reason to use the 32bit
haskell on OS X (aside from memory usage optimization cases which likely do
not matter to the *typical* user), and the community should probably update
the recommendation to reflect this.
I can certainly attest t
Hi,
I installed Haskell Platform 32-bit on a fresh 64-bit mac, because the
page http://www.haskell.org/platform/mac.html says: "Pick the 32-bit
vesion, unless you have a specific reason to use the 64-bit version.
The 32-bit one is slightly faster for most programs."
Then, during the installation
21 matches
Mail list logo
