From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/traceroute/
Date: Fri, 19 Feb 2016 01:58:54 +0000 (UTC) [thread overview]
Message-ID: <1455847124.a12c3e8288dfe7fb84e7d63b008a6b74770f655e.vapier@gentoo> (raw)
commit: a12c3e8288dfe7fb84e7d63b008a6b74770f655e
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 19 01:58:01 2016 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Fri Feb 19 01:58:44 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a12c3e82
net-analyzer/traceroute: fix cross-compiling #432116
net-analyzer/traceroute/traceroute-2.0.20.ebuild | 1 +
net-analyzer/traceroute/traceroute-2.0.21.ebuild | 1 +
2 files changed, 2 insertions(+)
diff --git a/net-analyzer/traceroute/traceroute-2.0.20.ebuild b/net-analyzer/traceroute/traceroute-2.0.20.ebuild
index f8af60f..ad19d1f 100644
--- a/net-analyzer/traceroute/traceroute-2.0.20.ebuild
+++ b/net-analyzer/traceroute/traceroute-2.0.20.ebuild
@@ -20,6 +20,7 @@ RDEPEND="!<net-misc/iputils-20121221-r1
src_compile() {
use static && append-ldflags -static
+ append-ldflags -L../libsupp #432116
tc-export AR CC RANLIB
emake env=yes
}
diff --git a/net-analyzer/traceroute/traceroute-2.0.21.ebuild b/net-analyzer/traceroute/traceroute-2.0.21.ebuild
index fef5017..4983e1f 100644
--- a/net-analyzer/traceroute/traceroute-2.0.21.ebuild
+++ b/net-analyzer/traceroute/traceroute-2.0.21.ebuild
@@ -20,6 +20,7 @@ RDEPEND="!<net-misc/iputils-20121221-r1
src_compile() {
use static && append-ldflags -static
+ append-ldflags -L../libsupp #432116
tc-export AR CC RANLIB
emake env=yes
}
next reply other threads:[~2016-02-19 1:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 1:58 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 7:44 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/traceroute/ Sam James
2024-02-03 6:56 Sam James
2024-02-02 13:45 Arthur Zamarin
2024-02-02 13:34 Arthur Zamarin
2024-02-02 6:40 Sam James
2024-02-02 3:58 Sam James
2023-12-24 17:21 Arthur Zamarin
2023-12-24 15:11 Sam James
2023-12-23 19:56 Arthur Zamarin
2023-12-20 10:04 Sam James
2023-08-31 5:29 Sam James
2023-05-01 13:36 Sam James
2023-03-04 17:54 Arthur Zamarin
2023-03-04 11:03 Arthur Zamarin
2023-03-04 9:55 Arthur Zamarin
2023-03-04 7:56 Arthur Zamarin
2023-03-04 6:17 Arthur Zamarin
2023-03-04 6:09 Arthur Zamarin
2023-03-04 5:32 Arthur Zamarin
2023-01-01 2:08 Sam James
2022-06-21 16:29 David Seifert
2022-05-26 5:06 WANG Xuerui
2022-04-03 2:48 Sam James
2021-09-23 1:07 Matt Turner
2021-07-16 1:31 Yixun Lan
2020-04-21 8:01 Jeroen Roovers
2019-03-31 22:37 Thomas Deutschmann
2019-01-29 11:52 Mikle Kolyada
2018-10-09 9:45 Mikle Kolyada
2018-10-06 23:47 Matt Turner
2018-10-06 23:47 Matt Turner
2018-10-02 20:10 Jeroen Roovers
2018-10-02 14:02 Tobias Klausmann
2018-10-01 0:07 Thomas Deutschmann
2018-09-30 23:03 Mart Raudsepp
2018-09-30 21:38 Sergei Trofimovich
2018-09-29 8:01 Sergei Trofimovich
2018-09-28 8:41 Mikle Kolyada
2016-03-09 8:02 Lars Wendler
2016-03-09 8:02 Lars Wendler
2016-02-19 1:58 Mike Frysinger
2016-02-19 1:58 Mike Frysinger
2016-02-19 1:58 Mike Frysinger
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=1455847124.a12c3e8288dfe7fb84e7d63b008a6b74770f655e.vapier@gentoo \
--to=vapier@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