Re: [Chicken-users] Bizarre chicken build/segfault problem

[Kon Lovett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 11, 2006, at 11:55 AM, Peter Bex wrote:

<snip>
> Aha, that explains.  I'm using the latest version, but I was looking
> in the Chicken svn repos, libc, ld.elf_so etc.  I never thought that
> the compilation would use another egg!  Stupid me :)

During compilation the needed eggs should only be necessary for  
checking imports. The actual code (*.scm, *.c, etc.) of the needed  
eggs shouldn't be touched. So no, not stupid you ;-).

(Except for syntax & include modules, but that isn't the issue here.)

> > You might as well also get the current locale, miscmacros, numbers, &
> > misc-extn eggs. These are also needed.
>
> They should be automatically installed right?  Anyway, I have them.

Yeah, but I had prophylactic measures in mind.

> > Hope you have a more productive time after re-installing.
>
> I'll try and trace the segfault I got on lookup-table.  Then I can get
> productive again :)

Was probably an undefined variable referenced from srfi-29. The  
lookup-table is compiled unsafe so this sort of thing will not be  
reported.

<snip>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iEYEARECAAYFAkUFuUcACgkQJJNoeGe+5O5t3ACdGuBBKpvSD5VlVbxqv4x1MfnH
p9YAn1azD4hCK8n0jjdX7TzFTnkMoj0b
=TOfp
-----END PGP SIGNATURE-----