I give up! Mac PPC doesn't like me now that I'm on Intel.
This is PPC, btw, and I _do_ have readline installed. GHC from
DarwinPorts compiles just fine.
../../ghc/compiler/stage1/ghc-inplace -o stage2/ghc-6.4.3 -H16m -O -
istage2/utils -istage2/basicTypes -istage2/types -istage2/hsSyn -
Thanks, you are absolutely right. There is an offset between the
function addresses defined in the link map and the addresses that show
up in gdb. I've rolled up my Jump to Conclusions mat.
Rich
Simon Marlow wrote:
Rich Fought wrote:
I'm getting into the weeds of a GHC-compiled program, and
On Jul 28, 2006, at 6:28 AM, Bulat Ziganshin wrote:
Hello Gregory,
Thursday, July 27, 2006, 11:06:41 PM, you wrote:
3. Did the threaded RTS work on 6.4.1? Was it used by default?
on 6.4.1 threaded RTS was used only in specially build libs. in
debugging versions of libs and GHCi single-thr
Hi Joel,
On Jul 28, 2006, at 7:50 AM, Joel Reymont wrote:
On Jul 28, 2006, at 11:42 AM, Simon Marlow wrote:
You shouldn't have to run configure again, but make clean definitely.
I still get the same allocateExec error. I'm still not sure how
updating configure.ac in ghc and making clean
Bulat Ziganshin wrote:
Hello Gregory,
Thursday, July 27, 2006, 11:06:41 PM, you wrote:
3. Did the threaded RTS work on 6.4.1? Was it used by default?
on 6.4.1 threaded RTS was used only in specially build libs. in
debugging versions of libs and GHCi single-threaded RTS was used.
developer
On 28 July 2006 12:50, Joel Reymont wrote:
> On Jul 28, 2006, at 11:42 AM, Simon Marlow wrote:
>
>> You shouldn't have to run configure again, but make clean definitely.
>
> I still get the same allocateExec error. I'm still not sure how
> updating configure.ac in ghc and making clean was going
On Jul 28, 2006, at 11:42 AM, Simon Marlow wrote:
You shouldn't have to run configure again, but make clean definitely.
I still get the same allocateExec error. I'm still not sure how
updating configure.ac in ghc and making clean was going to help :-).
--
http://wagerlabs.com/
__
Hello Gregory,
Thursday, July 27, 2006, 11:06:41 PM, you wrote:
> 3. Did the threaded RTS work on 6.4.1? Was it used by default?
on 6.4.1 threaded RTS was used only in specially build libs. in
debugging versions of libs and GHCi single-threaded RTS was used.
developers of threaded programs was
On 28 July 2006 11:39, Joel Reymont wrote:
> On Jul 28, 2006, at 11:11 AM, Simon Marlow wrote:
>
>> cvs update in ghc/, then 'make clean' and you should be all set.
>
> This is probably a silly question but I have never used cvs before. I
> assume cvs saved the CVSROOT and the password, is that
On Jul 28, 2006, at 11:11 AM, Simon Marlow wrote:
cvs update in ghc/, then 'make clean' and you should be all set.
This is probably a silly question but I have never used cvs before. I
assume cvs saved the CVSROOT and the password, is that right? Also, I
only saw
P configure.ac
Should
On 28 July 2006 10:54, Joel Reymont wrote:
> On Jul 28, 2006, at 8:47 AM, Simon Marlow wrote:
>
>> Ah, I see the problem. We added allocateExec() after the 6.4.2,
>> but the version in the source tree is still 6.4.2, so GHC thinks it
>> is safe to assume the two versions are the same, when in fa
On Jul 28, 2006, at 8:47 AM, Simon Marlow wrote:
Ah, I see the problem. We added allocateExec() after the 6.4.2,
but the version in the source tree is still 6.4.2, so GHC thinks it
is safe to assume the two versions are the same, when in fact the
6.4.2 you are bootstrapping with doesn't h
On Jul 28, 2006, at 8:58 AM, Simon Marlow wrote:
Hi Greg,
Gregory Wright wrote:
Some data and a few questions:
1. The failure on FreeBSD is not the same as on OS X. I built 6.4.2
from cvs on FreeBSD 6.1, and ran the ghc-regress tests. The tests
took a long time to run (about 14 hours on a d
On Jul 28, 2006, at 3:58 AM, Simon Marlow wrote:
Hi Greg,
Gregory Wright wrote:
Some data and a few questions:
1. The failure on FreeBSD is not the same as on OS X. I built 6.4.2
from cvs on FreeBSD 6.1, and ran the ghc-regress tests. The tests
took a long time to run (about 14 hours on a d
Rich Fought wrote:
I'm getting into the weeds of a GHC-compiled program, and need a little
help. I'm trying to chase down a memory leak and Valgrind gives me the
following:
==24390== 54,844 bytes in 639 blocks are definitely lost in loss record
69 of 69
==24390==at 0x400446D: malloc (vg
Hi Greg,
Gregory Wright wrote:
Some data and a few questions:
1. The failure on FreeBSD is not the same as on OS X. I built 6.4.2
from cvs on FreeBSD 6.1, and ran the ghc-regress tests. The tests
took a long time to run (about 14 hours on a dual Xeon 2.8 GHz
with 2 GB of memory). Towards the
Joel Reymont wrote:
It didn't take me long to discover allocateExec in ./ghc/rts/Storage.c.
I'm at a loss for clues as the build line that's trying to build stage1
ghc and barfing does not include anything from the rts directory.
Shouldn't it?
Ah, I see the problem. We added allocateExec(
17 matches
Mail list logo
