public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ams at toroid dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35365]  New: dlopen fails because of missing _Jv_RegisterClasses under HP-UX 11.11
Date: Mon, 25 Feb 2008 10:48:00 -0000	[thread overview]
Message-ID: <bug-35365-15820@http.gcc.gnu.org/bugzilla/> (raw)

I build the DBD::mysql Perl module under HP-UX 11.11 on an RP3440 machine with
GCC 4.2.1. The link looked like this:

LD_RUN_PATH="/usr/local/mysql/lib" /opt/perl_64/bin/perl myld gcc -shared
-static-libgcc -fPIC -L/lib/pa20_64 dbdimp.o mysql.o -o
blib/arch/auto/DBD/mysql/mysql.sl -L/usr/local/mysql/lib
-L/opt/hp-gcc64-4.2.1/lib/gcc/hppa64-hp-hpux11.11/4.2.1 -lmysqlclient -lz -lnsl
-lm -lgcc

The module built fine, but its "make test" failed with the following error.

/usr/lib/pa20_64/dld.sl: Unsatisfied code symbol '_Jv_RegisterClasses' in load
module '/mnt/DBD-mysql-4.006/blib/arch/auto/DBD/mysql/mysql.sl'

I solved this problem by linking in a stub.o that contained an empty definition
of _Jv_RegisterClasses. Apparently the problem is that the HP-UX dynamic linker
does not just ignore unresolvable weak symbols as it should, so it's not a gcc
bug, but perhaps the symbol should be exported by default, since the weak
definition has already been removed for HP-UX in this patch:

http://gcc.gnu.org/ml/gcc-patches/2006-04/msg00327.html


-- 
           Summary: dlopen fails because of missing _Jv_RegisterClasses
                    under HP-UX 11.11
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ams at toroid dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35365


                 reply	other threads:[~2008-02-25 10:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-35365-15820@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).