This is the mail archive of the
mailing list for the GCC project.
[Bug libfortran/21185] libgfortran unusable for cross-testing for newlib targets
- From: "hp at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Sep 2007 21:31:18 -0000
- Subject: [Bug libfortran/21185] libgfortran unusable for cross-testing for newlib targets
- References: <firstname.lastname@example.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #18 from hp at gcc dot gnu dot org 2007-09-14 21:31 -------
(In reply to comment #17)
> We'll see whether the test-results are meaningful; it's likely there's more to
Unfortunately not very meaningful without a getcwd. I got curious why getcwd
would be needed, so I looked around, and it seems the stored absolute exe path
is only reachable by full_exe_path(), called only from
- which is #if GLIBC_BACKTRACE'd out; empty for newlib targets!
So, I'll update your patch to get rid of the getcwd call, attach the result and
start a new test.