newlib and the use of fcntl by java

Wed Sep 25 05:43:00 GMT 2002

> What we used to do was stub out the Posix-dependent stuff for an
> embedded target. See this in configure.host:
>> xscale*-elf)
> 	with_libffi_default=no
> 	PROCESS=Ecos
> 	FILE=Posix
> 	CHECKREFSPEC=-fcheck-references
> 	EXCEPTIONSPEC=
> 	enable_java_net_default=no
> 	enable_getenv_properties_default=no
> 	enable_main_args_default=no
> 	;;
>> So we should *not* be loading natPosixProcess.cc on an embedded ARM
> target. Is the problem not simply that an entry in configure.host
> hasn't been created for embedded ARM?

If it doesn't do it for XScale it doesn't do it for my ARM configuration 
(since it's a copy of the XScale one) -- after all, an XScale chip is an 
arm ;-)
I was just grepping through the sources for places where fcntl was being 
called from. I didn't check to see if the configuration disabled that 
particular code file, though I do know that something calling fcntl was 
being linked in since that was causing the linkage failures.
Things are looking fairly good now on arm-elf for libjava -- 18 unexpected 
failures vs 8 on arm-linux running natively.
I must get my changes checked in....
R.