CHICKEN Scheme

Summary

undefined reference to `C_chicken_syntax_toplevel' compiling experimental branch

Metadata

Id: c1932b2f01460333b268ac4170d86577589f4629
Trac id: 463
Type: defect
Reporter: alanpost
Owner:
Cc: alanpost@sunflowerriver.org
Status: closed
Component: build system
Estimated difficulty:
Resolution: invalid
Priority: major
Milestone: 4.9.0
Version: 4.6.x
Changetime: 2012-09-24 21:47:48 UTC
Created: 2010-12-19 23:29:10 UTC
Keywords:

After working with C-Keen to introduce a patch to bypass ticket:462, I've continued trying to compile the experimental branch of Chicken on OpenBSD 4.8. If you pretend that ticket:462 is fixed, the build continues and produces the following error:

 gcc  -L. chicken.o batch-driver.o compiler.o optimizer.o compiler-syntax.o scrutinizer.o unboxing.o support.o c-platform.o c-backend.o -o chicken \
           -lchicken -Wl,-R"." -lm
 ./libchicken.so: warning: strcpy() is almost always misused, please use strlcpy()
 ./libchicken.so: warning: sprintf() is often misused, please use snprintf()
 ./libchicken.so: warning: strcat() is almost always misused, please use strlcat()
 chicken.o(.text+0x1f4e): In function `f_99':
 : undefined reference to `C_chicken_syntax_toplevel'
 collect2: ld returned 1 exit status
 gmake[1]: *** [chicken] Error 1
 gmake[1]: Leaving directory `/home/a/wa/chicken/core'
 gmake: *** [all] Error 2

Changes and comments

[2010-12-19 23:30:27 UTC] alanpost set cc to alanpost@sunflowerriver.org

[2010-12-20 10:26:39 UTC] ckeen wrote:

Which chicken did you use to compile this one? I can build chicken just fine using 4.6.0 and the recent experimental branch on OpenBSD 4.8 (with the patch of Bug #462)

[2010-12-20 19:36:51 UTC] alanpost changed status from new to closed

[2010-12-20 19:36:51 UTC] alanpost set resolution to invalid

[2010-12-20 19:36:51 UTC] alanpost wrote:

Replying to ckeen: > Which chicken did you use to compile this one? > I can build chicken just fine using 4.6.0 and the recent experimental branch on OpenBSD 4.8 (with the patch of Bug #462)

I've bootstrapped from Chicken 4.6.0 and this problem no longer occurs.