public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: dev-libs/intel-common/
Date: Thu, 19 May 2011 05:56:27 +0000 (UTC)	[thread overview]
Message-ID: <bfb13f5158483165b5c994a83ed51116e070d782.jlec@gentoo> (raw)

commit:     bfb13f5158483165b5c994a83ed51116e070d782
Author:     Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Thu May 19 05:55:26 2011 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Thu May 19 05:55:26 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=bfb13f51

Add missing path to LDPATH, #367959

(Portage version: 2.2.0_alpha34/git/Linux x86_64, unsigned Manifest commit)

---
 dev-libs/intel-common/ChangeLog                    |    3 +++
 .../intel-common/intel-common-12.0.2.137.ebuild    |    2 +-
 2 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/dev-libs/intel-common/ChangeLog b/dev-libs/intel-common/ChangeLog
index 7a69e6e..304d54d 100644
--- a/dev-libs/intel-common/ChangeLog
+++ b/dev-libs/intel-common/ChangeLog
@@ -2,6 +2,9 @@
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+  19 May 2011; Justin Lecher <jlec@gentoo.org> intel-common-12.0.2.137.ebuild:
+  Add missing path to LDPATH, #367959
+
   31 Mar 2011; Justin Lecher <jlec@gentoo.org> intel-common-12.0.2.137.ebuild:
   Corrected env.d files creation
 

diff --git a/dev-libs/intel-common/intel-common-12.0.2.137.ebuild b/dev-libs/intel-common/intel-common-12.0.2.137.ebuild
index 7d84a77..b4679aa 100644
--- a/dev-libs/intel-common/intel-common-12.0.2.137.ebuild
+++ b/dev-libs/intel-common/intel-common-12.0.2.137.ebuild
@@ -48,7 +48,7 @@ src_install() {
 	for arch in ${INTEL_ARCH}; do
 			path=${path}:${INTEL_SDP_EDIR}/bin/${arch}:${INTEL_SDP_EDIR}/mpirt/bin/${arch}
 			rootpath=${rootpath}:${INTEL_SDP_EDIR}/bin/${arch}:${INTEL_SDP_EDIR}/mpirt/bin/${arch}
-			ldpath=${ldpath}:${INTEL_SDP_EDIR}/compiler/lib/${arch}
+			ldpath=${ldpath}:${INTEL_SDP_EDIR}/compiler/lib/${arch}:${INTEL_SDP_EDIR}/mpirt/lib/${arch}
 	done
 	cat >> ${fenv} <<-EOF
 		PATH=${path#:}



             reply	other threads:[~2011-05-19  5:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19  5:56 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-19  6:31 [gentoo-commits] proj/sci:master commit in: dev-libs/intel-common/ Justin Lecher
2011-05-19  7:21 Justin Lecher
2011-05-28  7:49 Justin Lecher
2011-05-28 11:50 Justin Lecher
2011-10-25 17:16 Justin Lecher
2012-02-16 22:35 Sebastien Fabbro
2012-09-20 12:45 Justin Lecher
2012-10-07  9:18 Justin Lecher
2012-11-27 19:33 Justin Lecher
2012-11-27 19:33 Justin Lecher
2012-12-10 21:29 Justin Lecher
2016-02-15  8:19 Justin Lecher
2016-02-15  8:19 Justin Lecher
2016-02-19  9:27 Justin Lecher
2016-02-19 10:12 Justin Lecher
2018-01-27 12:24 Justin Lecher
2018-04-03  3:52 Matthias Maier
2018-04-03 16:44 Matthias Maier
2018-04-03 16:44 Matthias Maier
2019-05-22 16:18 Horea Christian
2019-05-25  6:36 Matthias Maier
2020-05-05  6:30 Matthias Maier
2021-01-30 14:55 Andrew Ammerlaan

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=bfb13f5158483165b5c994a83ed51116e070d782.jlec@gentoo \
    --to=jlec@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