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
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
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 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
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
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
Good idea! Done.
Mario Domenech Goulart wrote:
What do you think about making a link to this file? Maybe at
http://chicken.wiki.br/platforms?
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chi
