Re: [ECOS] removing FILEIO causes compiler errors

[Jonathan Larmour <jlarmour at redhat dot com>]

"Trenton D. Adams" wrote:
> 
> CYGPKG_LIBC_STDIO_FILEIO can't be disabled, it's greyed out.

That's because it is disabled if fileio has been removed.
 
> I assume that's what's causing the compiler error below!?
> 
> make[1]: Leaving directory
> `/c/MyDocuments/eCosBuilds/RAMSupport_build/devs/eth/arm/edb7xxx/current
> '
> In file included from
> /cygdrive/C/MyDocuments/eCosBuilds/RAMSupport_install/include/machine/li
> mits.h:59,
> make: Leaving directory `/c/MyDocuments/eCosBuilds/RAMSupport_build'
>                  from
> /cygdrive/C/MyDocuments/eCosBuilds/RAMSupport_install/include/sys/param.
> h:167,
>                  from
> /cygdrive/C/MyDocuments/eCosBuilds/RAMSupport_install/include/eth_drv.h:
> 63,
>                  from
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/devs/eth/arm/edb7xx
> x/current/src/if_edb7xxx.c:70:
> /cygdrive/C/MyDocuments/eCosBuilds/RAMSupport_install/include/limits.h:1
> 66: cyg/fileio/limits.h: No such file or directory
> make[1]: *** [src/if_edb7xxx.o.d] Error 1
> make: *** [build] Error 2
> 
> If not, there's something wrong happening when I remove the FILEIO
> package.

No, but I know what that is: an earlier run set an inferred value. You've
changed the configuration, but the inferred values don't get reverted. This
has caused confusion before, and I think it should be changed (but no time
as usual, alas). At a guess you could hack around with something like:

sed '/inferred_value/d' < ecos.ecc > ecos.foo
mv ecos.foo ecos.ecc

Untested of course :-).

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine