From: Alexey Tourbin <at@altlinux.ru>
To: devel@altlinux.ru
Subject: [devel] slatec, fortran libraries, weak symbols
Date: Sat, 27 Nov 2004 00:26:49 +0300
Message-ID: <20041126212649.GI31657@solemn.turbinal.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Здравствуйте.
Библиотека slatec собирается так:
for f in *.f; do g77 -c %optflags %optflags_shared "$f"; done
g77 -shared -o lib%name.so.%version -Wl,-soname=lib%name.so.%version *.o
echo 'main(){}' >ldtest.c
gcc ldtest.c lib%name.so.%version
В результате получается:
+ gcc ldtest.c libslatec.so.4.1
libslatec.so.4.1: undefined reference to `dgvec_'
libslatec.so.4.1: undefined reference to `uvec_'
libslatec.so.4.1: undefined reference to `uivp_'
libslatec.so.4.1: undefined reference to `duvec_'
libslatec.so.4.1: undefined reference to `duivp_'
libslatec.so.4.1: undefined reference to `gvec_'
libslatec.so.4.1: undefined reference to `dfmat_'
libslatec.so.4.1: undefined reference to `fmat_'
collect2: ld returned 1 exit status
При изучения исходников выяснилось следующее (цитирую из dbvsup.f):
C The user must supply subroutines DFMAT, DGVEC, DUIVP and DUVEC,
C when needed (they must be so named), to evaluate the derivatives
C as follows
C
C A. DFMAT must be supplied.
Т.е. функции, которые должны быть определены пользователем, на практике
оборачиваются undefined references в библиотеке. Подозреваю, что эта
проблема может быть решена с помощью weak symbols. Кто-нибудь знает,
как именно?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-11-26 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 21:26 Alexey Tourbin [this message]
2004-11-26 21:30 ` Dmitry V. Levin
2004-11-29 5:35 ` Constantin Mikhaylenko
2004-11-29 11:04 ` [devel] " Alexey Tourbin
2004-11-29 11:25 ` Constantin Mikhaylenko
2004-11-29 12:51 ` Alexey Tourbin
2004-11-30 14:57 ` Alexey Tourbin
2004-11-30 15:46 ` Dmitry V. Levin
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=20041126212649.GI31657@solemn.turbinal.org \
--to=at@altlinux.ru \
--cc=devel@altlinux.ru \
/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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git