close depends on fclose?!

[Sam Steingold]

Hi
Why does close depend on fclose?!
It seems that, close being a system call and fclose being a C library
function, the dependency should be the other way around: fclose should
depend on close, but _NOT_ vice versa.
E.g., CLISP uses close but never FILE or fclose et al, so, when pulling
close, which pulled fclose, I got all these files which I will NEVER need:

? src/gllib/fclose.c
? src/gllib/fflush.c
? src/gllib/fpurge.c
? src/gllib/freading.c
? src/gllib/freading.h
? src/gllib/fseek.c
? src/gllib/fseeko.c
? src/gllib/ftell.c
? src/gllib/ftello.c
? src/gllib/stdio-impl.h
? src/gllib/stdio.in.h
? src/glm4/fclose.m4
? src/glm4/fflush.m4
? src/glm4/fpurge.m4
? src/glm4/freading.m4
? src/glm4/fseek.m4
? src/glm4/fseeko.m4
? src/glm4/ftell.m4
? src/glm4/ftello.m4
? src/glm4/stdio_h.m4

Could you please make close independent on stdio?
Thanks!

-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 
11.0.60900031
http://www.PetitionOnline.com/tap12009/ http://memri.org http://ffii.org
http://camera.org http://truepeace.org http://openvotingconsortium.org
UNIX is as friendly to you as you are to it. Windows is hostile no matter what.