On 9/11/06, Peter Bex [EMAIL PROTECTED] wrote:
The reason I'm posting here is that there is one thing that baffles me:
When running a backtrace with GDB, it tells me the error occurs in a
function in lookup-table.c. But I can't find this file (or
lookup-table.scm) anywhere!
Hi, Peter!
On Tue, Sep 12, 2006 at 08:15:22AM +0200, felix winkelmann wrote:
Hi, Peter!
lookup-table.c is one source file of the lookup-table egg. The .c files
are installed together with a compiled extension.
The reason for the crash seems to be egg-dependency issues.
I could reproduce a crash that
On 9/12/06, Peter Bex [EMAIL PROTECTED] wrote:
LIST ALL (that is: A-L-L) DIRECTLY AND _INDIRECTLY_ USED EXTENSIONS
IN YOUR *.META FILES!!!
This is Really Bad News. I'm having another error (this time a bus error)
and figuring out where in the egg dependency chain this is caused will be
one
On Mon, 11 Sep 2006, Brandon J. Van Every wrote:
[...] Seems pretty important if removing the bootstrap compiler toasts
the installation. [...]
Hello,
removing the bootstrap compiler only toasts the installed chicken-static
and csi-static, not chicken and csi. And so far I have *never* had
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
On Mon, 11 Sep 2006, Brandon J. Van Every wrote:
[...] But, we'll see if my INCLUDE_DIRECTORIES bulletproofing has any
effect on this problem. [...]
Hello,
I just pulled the latest changes using darcs and rebuilt
{chicken,csi}-static with CMake -- I still get dynamically linked
-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
Shouldn't the initial output port in Chicken applications
be line-buffered? I think this is the standard practice in most
programming languages, but it seems not to be the case with Chicken
(I'm using 2.3 in GNU/Linux).
In the specific case of C, at least in GNU/Linux with glibc:
The stream
Thanks guys for the responses.
Another related question...
If I allocate memory in Chicken using a byte-vector and pass this over
to C, what happens if the C code consumes the memory and does a
realloc on its pointer? I am guessing Chicken (byte-vector-length)
would just not know about any
Ok thanks, I understand what route to take now.
Cheers,
John.
On 12/09/06, Kon Lovett [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 12, 2006, at 12:01 PM, john wrote:
Thanks guys for the responses.
Another related question...
If I allocate memory in
Thomas Chust wrote:
On Mon, 11 Sep 2006, Brandon J. Van Every wrote:
[...] Seems pretty important if removing the bootstrap compiler
toasts the installation. [...]
Hello,
removing the bootstrap compiler only toasts the installed
chicken-static and csi-static, not chicken and csi. And so
11 matches
Mail list logo
