public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: craig_files@agilent.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/4881: errno_location() not linked when creating static library
Date: Sun, 04 Nov 2001 02:33:00 -0000 [thread overview]
Message-ID: <20011115153705.26022.qmail@sourceware.cygnus.com> (raw)
>Number: 4881
>Category: c++
>Synopsis: errno_location() not linked when creating static library
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Nov 15 07:46:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Craig Files
>Release: gcc version 3.0.2 20010905
>Organization:
>Environment:
(Red Hat Linux 7.1 3.0.1-3) and
(hppa1.1-hp-hpux11.00)
the linux configure setup:
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux
>Description:
Creating static libraries the *errno_location() is not
declared. This is a problem when loading the shared libraries
into TCL because it wants everything defined :
libddftcl.so: undefined symbol: _Z16__errno_locationv
where libddftcl.so is the shared library
linked by
g++ -shared *.lo -Wl,--whole-archive *.al *.a -Wl,-soname -Wl,libddftcl.so.0 -o .libs/libddftcl.so.0.0.0
>How-To-Repeat:
create shared libraries and try to load them in tcl or
evaluate if errno_location is defined
>Fix:
define errno_location when building shared libraries
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-11-15 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 2:33 craig_files [this message]
2001-11-06 11:56 rodrigc
2001-11-06 13:18 rodrigc
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=20011115153705.26022.qmail@sourceware.cygnus.com \
--to=craig_files@agilent.com \
--cc=gcc-gnats@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).