This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/21185] libgfortran unusable for cross-testing for newlib targets
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jan 2007 16:51:53 -0000
- Subject: [Bug libfortran/21185] libgfortran unusable for cross-testing for newlib targets
- References: <bug-21185-507@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from pinskia at gcc dot gnu dot org 2007-01-05 16:51 -------
(In reply to comment #4)
> I guess we could try to provide a graceful degradation for such systems... The
> use of dup() can probably be avoided if dup() isn't available, without too much
> degradation in the library features. access() can probably be emulated, or at
> least its basic features. For ftruncate(), however, I don't see how to make it
> work.
Except for newlib for spu-elf actually has dup, access and ftruncate now so
this is not a generic newlib issue really.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21185