[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Bizarre chicken build/segfault problem
From: |
Kon Lovett |
Subject: |
Re: [Chicken-users] Bizarre chicken build/segfault problem |
Date: |
Tue, 12 Sep 2006 06:12:33 -0700 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sep 12, 2006, at 4:46 AM, felix winkelmann wrote:
Attached is a patch for chicken-setup.scm that should really, really
handle dependencies correctly.
This doesn't sort out all problems, though: the generic setup-
header.scm
in most of Kon's extensions passes -X easyfii and -X dollar to
compilation
commands, but doesn't list them in the "need" clause in the respective
meta files. This is bad. I recommend to remove this and pass the -X
options explicitly. Another, suboptimal measure is to list them in the
need clause of all eggs that use setup-header.scm.
Kon, could you fix this, please?
Yes. Sorry, a late, too quick "easy fix" on my part. I just ASSumed
people using late-model Chicken would have these.
(FWIW, the above is very recent so it shouldn't effect too many
people. I will post updates today of everything.)
As for the ordering of needed eggs:
1) For the time being I suggest people watch the messages from setup
for "egg not installed". If they see one stop the build, setup the
egg separately, & restart the previous build.
2) Assume the (needs ...) list a partial order. Then recursively
extend each reference w/ its' references, until bottom. Then the list
would be a topological sort of the dependencies. Setup the resulting
list in order.
baz
(needs foo bar)
foo
(needs abc nbc)
abc
nbc
bar
=>
(needs abc nbc foo bar)
cheers,
felix
<chicken-setup.scm.diff>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iEYEARECAAYFAkUGskIACgkQJJNoeGe+5O67VgCaAp6PIQV5p+QR5PxATMVSOmtH
DGwAn1BDB5n743IzbCkxLCtLoPSEe1g5
=M4OI
-----END PGP SIGNATURE-----