From: Andy Wingo <wingo@pobox.com>
To: Leo <sdl.web@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: guile stable-2.0 fails on OSX 10.6.7
Date: Mon, 04 Apr 2011 22:44:09 +0200 [thread overview]
Message-ID: <m38vvpu4py.fsf@unquote.localdomain> (raw)
In-Reply-To: <m1wrja8mz1.fsf@th041153.ip.tsinghua.edu.cn> (Leo's message of "Mon, 04 Apr 2011 16:00:50 +0800")
On Mon 04 Apr 2011 10:00, Leo <sdl.web@gmail.com> writes:
> On 2011-04-04 15:13 +0800, Andy Wingo wrote:
>>> cc1(57938) malloc: *** error for object 0x10357a148: incorrect checksum for freed object - object was probably modified after being freed.
>>> *** set a breakpoint in malloc_error_break to debug
>>> vm-engine.c: In function 'vm_regular_engine':
>>> vm-engine.c:38: internal compiler error: Abort trap
>>> Please submit a full bug report,
>>> with preprocessed source if appropriate.
>>> See <URL:http://developer.apple.com/bugreporter> for instructions.
>>
>> This is an internal error in Apple's C compiler. Try a different one.
>
> In that case, I'll stick to my current version of guile. I am not
> familiar with C and all other packages I have installed from source work
> fine at the moment. I have also compiled racket from source, no problem
> at all.
Sorry, didn't mean to sound hostile there. I don't know anything about
Mac OS 10.6. However if it is still the case that they ship something
called gcc and something called gcc-4.2, you can compile with
./configure ... CC=gcc-4.2, and you probably get better results.
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-04-04 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 15:02 guile stable-2.0 fails on OSX 10.6.7 Leo
2011-04-03 20:07 ` Andy Wingo
2011-04-04 2:01 ` Leo
2011-04-04 7:13 ` Andy Wingo
2011-04-04 8:00 ` Leo
2011-04-04 20:44 ` Andy Wingo [this message]
2011-04-05 2:42 ` Leo
2011-04-27 14:30 ` Mark H Weaver
2011-04-27 16:33 ` Leo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38vvpu4py.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=sdl.web@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).