Hello,
After installing, everything seems to give the error message:
`##sys#error-hook' is not defined - the `library' unit was probably not linked
with this executable - execution terminated
Benedikt
___
Chicken-users mailing list
Chicken-users@
Hi Benedikt,
On Fri, 24 Aug 2007 19:40:43 +0200 Benedikt Rosenau <[EMAIL PROTECTED]> wrote:
> After installing, everything seems to give the error message:
>
> `##sys#error-hook' is not defined - the `library' unit was probably not
> linked with this executable - execution terminated
>Bened
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 24, 2007, at 2:50 PM, Mario Domenech Goulart wrote:
Hi Benedikt,
On Fri, 24 Aug 2007 19:40:43 +0200 Benedikt Rosenau
<[EMAIL PROTECTED]> wrote:
After installing, everything seems to give the error message:
`##sys#error-hook' is not de
Hi there.
There was a change made to the blob-handling code in SVN r5529
(2007-08-19) which caused this error. You cannot build 5529 or later
unless you already have a pretty recent compiler installed for the
bootstrap phase. I don't know exactly how recent yet, but it's
definitely sometime afte
This issue should now be fixed in SVN head. The culprit was the use
of the 'optional' macro, which was introduced (renamed) in 2.622,
preventing bootstrap by earlier compilers.
On 8/26/07, Zbigniew <[EMAIL PROTECTED]> wrote:
> There was a change made in SVN r5529 which caused this error.
__
Hello all,
Thanks to Zbigniew, I got a newer version of Chicken to work.
To spell it out in detail:
Install chicken-2.6 from the webpage.
Download the snapshot chicken-2.636.
Go to a directory and execute the following:
$ svn co -r 5361 https://galinha.ucpel.tche.br/svn/chicken-eggs/chicken/tr
Sorry if I wasn't more clear--
You can simply download the latest SVN snapshot (5752) now and compile
it with any compiler (including chicken-2.6). You don't have to
install an intermediate compiler.
Also, in general it's not necessary to copy any configure (etc.) files
over; these are automatic
On Mon, Aug 27, 2007 at 12:03:56PM -0500, Zbigniew wrote:
> You can simply download the latest SVN snapshot (5752) now and compile
> it with any compiler (including chicken-2.6). You don't have to
> install an intermediate compiler.
I thought again I had found the most complicated way to do some
Hi Benedikt,
On Thu, 30 Aug 2007 15:03:53 +0200 Benedikt Rosenau <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 27, 2007 at 12:03:56PM -0500, Zbigniew wrote:
>
> > You can simply download the latest SVN snapshot (5752) now and compile
> > it with any compiler (including chicken-2.6). You don't have t
Hi Mario,
> Try
> $ LD_LIBRARY_PATH=/path/to/chicken-prefix/lib csi
Thank you, I knew. What I meant is that this should be done
in the setup/install scripts as it was done before. I think
it is better when a system does run after installation, and
that the fact is tested. I hope I do not get on a
We need more information--installation should work without a problem,
and has been tested to work. What path did you install Chicken into?
What options did you provide to configure? What steps did you follow
to build it, exactly?
On 8/30/07, Benedikt Rosenau <[EMAIL PROTECTED]> wrote:
> Hi Mario
Hi Zbigniew,
So far I just followed the procedure:
$ svn co https://galinha.ucpel.tche.br/svn/chicken-eggs/chicken/trunk
$ cd trunk
$ sh autogen.sh
$ make CHICKEN=`which chicken`
$ make install
Regards,
Benedikt
___
Chicken-users mailing list
Chic
The trunk doesn't include a Makefile, so it would be impossible to run
make without running configure first. Did you run ./configure?
On 8/30/07, Benedikt Rosenau <[EMAIL PROTECTED]> wrote:
> So far I just followed the procedure:
> $ svn co https://galinha.ucpel.tche.br/svn/chicken-eggs/chicken/t
On 8/30/07, Benedikt Rosenau <[EMAIL PROTECTED]> wrote:
> Hi Mario,
>
> > Try
> > $ LD_LIBRARY_PATH=/path/to/chicken-prefix/lib csi
>
> Thank you, I knew. What I meant is that this should be done
> in the setup/install scripts as it was done before. I think
> it is better when a system does run aft
Hi Felix,
Although I haven't been able to track this down (compilation works for
me), this is the output for Benedikt's ldd:
$ ldd `which csi`
linux-gate.so.1 => (0xe000)
libchicken.0 => not found
libdl.so.2 => /lib/libdl.so.2 (0xb7f75000)
libm.so.6 => /lib/libm.s
On 9/1/07, Zbigniew <[EMAIL PROTECTED]> wrote:
> Hi Felix,
>
> Although I haven't been able to track this down (compilation works for
> me), this is the output for Benedikt's ldd:
>
> $ ldd `which csi`
>linux-gate.so.1 => (0xe000)
>libchicken.0 => not found
>libdl.so.2
Benedikt,
Elf mentioned to me that this could be a libtool problem. Could you
report the version number returned by these commands:
libtool --version
libtoolize --version
aclocal --version
autoheader --version
automake --version
autoconf --version
The build output you provided to me shows that
On Sat, Sep 01, 2007 at 07:12:20PM +0200, felix winkelmann wrote:
> I assume some build broke there. Or probably some leftovers from
> old installs. Removing remnants like this and installing from scratch
> should help in any case.
I am not sure how to interpret this. I need a working chicken for
Hi Benedikt,
On Mon, 3 Sep 2007 15:24:04 +0200 Benedikt Rosenau <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 01, 2007 at 07:12:20PM +0200, felix winkelmann wrote:
>
> > I assume some build broke there. Or probably some leftovers from
> > old installs. Removing remnants like this and installing from
On Mon, Sep 03, 2007 at 10:31:50AM -0300, Mario Domenech Goulart wrote:
>> I am not sure how to interpret this. I need a working chicken for
>> the installation of 2.637 - or not?
> You don't need it. Just grab the snapshot from, say,
> http://chicken.wiki.br/dev-snapshots/2007/09/01 and build i
20 matches
Mail list logo
