From: "Sebastien Fabbro (bicatali)" <bicatali@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-libs/libf2c/files: 20070912-link-shared-libf2c-correctly.patch
Date: Thu, 06 Nov 2008 15:05:15 +0000 [thread overview]
Message-ID: <E1Ky6Q7-00057K-M7@stork.gentoo.org> (raw)
bicatali 08/11/06 15:05:15
Modified: 20070912-link-shared-libf2c-correctly.patch
Log:
Really including soname into shared library
(Portage version: 2.2_rc12/cvs/Linux 2.6.25-gentoo-r7 x86_64)
Revision Changes Path
1.2 dev-libs/libf2c/files/20070912-link-shared-libf2c-correctly.patch
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libf2c/files/20070912-link-shared-libf2c-correctly.patch?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libf2c/files/20070912-link-shared-libf2c-correctly.patch?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libf2c/files/20070912-link-shared-libf2c-correctly.patch?r1=1.1&r2=1.2
Index: 20070912-link-shared-libf2c-correctly.patch
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-libs/libf2c/files/20070912-link-shared-libf2c-correctly.patch,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- 20070912-link-shared-libf2c-correctly.patch 8 Jul 2008 06:40:45 -0000 1.1
+++ 20070912-link-shared-libf2c-correctly.patch 6 Nov 2008 15:05:15 -0000 1.2
@@ -5,7 +5,7 @@
libf2c.so: $(OFILES)
- cc -shared -o libf2c.so $(OFILES)
-+ $(CC) -shared -lm -o libf2c.so $(OFILES)
++ $(CC) -shared -Wl,-soname,libf2c.so.2 -lm -o libf2c.so.2 $(OFILES)
### If your system lacks ranlib, you don't need it; see README.
next reply other threads:[~2008-11-06 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 15:05 Sebastien Fabbro (bicatali) [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 6:40 [gentoo-commits] gentoo-x86 commit in dev-libs/libf2c/files: 20070912-link-shared-libf2c-correctly.patch Donnie Berkholz (dberkholz)
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=E1Ky6Q7-00057K-M7@stork.gentoo.org \
--to=bicatali@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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