From: "Neil Jerram" <neiljerram@googlemail.com>
To: tantalum <theseph@gmx.de>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.8.5 compile segfault
Date: Sat, 20 Sep 2008 00:48:26 +0200 [thread overview]
Message-ID: <49dd78620809191548j7cd047a6ted13d3948a26c2c7@mail.gmail.com> (raw)
In-Reply-To: <48D3CFF8.1010105@gmx.de>
Hi...
2008/9/19 tantalum <theseph@gmx.de>:
> hi
>
> having dependencies
> gmp 4.2.2-2
> libtool 2.2.6a-1
> installed and 64bit linux,
> im trying to compile guile 1.8.5, but it fails leaving the message found
> here:
> http://pastebin.com/m3bd2e879
> "Speicherzugriffsfehler" translates to "segmentation fault"
A problem very similar to that was fixed by these commits, since the
1.8.5 release:
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=9143131b2766d1e29e05d61b5021395b4c93a6bc
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=c67a68f4f14bc0bdc11c1dca37eae7f610432a49
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=adacd2dac5ad1c80a8faf8933c228533fb82cc80
> this happens also with the git version.
What do you mean, exactly? (If you mean the head of the
branch_release-1-8 branch, I guess this must be a new problem.)
> im clueless, can i do something?
> i really like guile, and like to use the newest version because it fixed a
> bug with g-wrap.
It depends if this is a new problem, or one that we have fixed - so I
need your answer to the question just above.
Regards,
Neil
next prev parent reply other threads:[~2008-09-19 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 16:14 guile 1.8.5 compile segfault tantalum
2008-09-19 22:48 ` Neil Jerram [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-20 13:31 tantalum
2008-09-21 9:43 ` Neil Jerram
2008-09-21 13:01 tantalum
2008-09-21 21:27 ` Neil Jerram
2008-09-22 17:25 tantalum
2008-09-22 19:29 ` Neil Jerram
2008-09-23 18:35 tantalum
2008-10-13 22:38 ` Neil Jerram
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=49dd78620809191548j7cd047a6ted13d3948a26c2c7@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=bug-guile@gnu.org \
--cc=theseph@gmx.de \
/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).