This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/49314] md5test, shatest output FAILs on Tru64 UNIX
- From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 17 Jun 2011 14:02:17 +0000
- Subject: [Bug libgcj/49314] md5test, shatest output FAILs on Tru64 UNIX
- Auto-submitted: auto-generated
- References: <bug-49314-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49314
Jack Howarth <howarth at nitro dot med.uc.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |howarth at nitro dot
| |med.uc.edu
--- Comment #9 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-06-17 14:01:23 UTC ---
(In reply to comment #8)
> > --- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-06-17 13:04:17 UTC ---
> > Could this pr be related to pr49441?
>
> No: the iconv functions only live in libiconv (no stubs in libc), and
> that is present in libgcj.spec and linked into the test programs.
>
> Rainer
pr49441 is a totally different issue. That bug manifests itself as a runtime
error with unresolved symbols from libiconv. I still don't understand why we
just don't link libgcj directly against libiconv to avoid needing libgcj.spec
to pass anything for libiconv.