From: "Andrea Arteaga" <andyspiros@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/auto-numerical-bench:master commit in: numbench/, doc/
Date: Fri, 19 Aug 2011 11:45:49 +0000 (UTC) [thread overview]
Message-ID: <956c17a127d65428d8cece41844c07fa3833f585.spiros@gentoo> (raw)
commit: 956c17a127d65428d8cece41844c07fa3833f585
Author: Andrea Arteaga <andyspiros <AT> gmail <DOT> com>
AuthorDate: Fri Aug 19 11:45:41 2011 +0000
Commit: Andrea Arteaga <andyspiros <AT> gmail <DOT> com>
CommitDate: Fri Aug 19 11:45:41 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/auto-numerical-bench.git;a=commit;h=956c17a1
Updated documentation and allow more environment bash files.
---
doc/numbench.1 | 16 ++++++++++++++++
numbench/main.py | 4 +++-
2 files changed, 19 insertions(+), 1 deletions(-)
diff --git a/doc/numbench.1 b/doc/numbench.1
index f7c3905..e429c8b 100644
--- a/doc/numbench.1
+++ b/doc/numbench.1
@@ -88,6 +88,22 @@ atlas-gcc-4.6.1 sci-libs/atlas-3.9.46 CC=gcc-4.6.1 CFLAGS="-O3 -march=native"
.PP
Variables that affect the emerge process, such as USE, can be used
and are effective.
+Another possibility to set the environment used during the emerge process is
+writing a bash script that uses the export directives. These files have to be
+specified added to the line with a leading @ mark. More files can be specified;
+in this case the latter files override the variables in case of collisions;
+the environment variables that are specified on the configuration line override
+the variables set through files in case of collisions. The files can be
+specified with both a relative path or an absolute one. The following examples
+show this feature:
+
+.RS
+atlas-gcc sci-libs/atlas-3.9.46 @envforatlas.sh @envforgcc
+
+atlas-gcc sci-libs/atlas-3.9.46 @envforatlas.sh CC=gcc-4.6.1 CFLAGS="-O3"
+.RE
+
+.PP
More configuration options are available. As each package can
install many implementations of the same library (for instance, the
sci-libs/atlas package installs the serial version and the
diff --git a/numbench/main.py b/numbench/main.py
index 58e5e58..bab534f 100755
--- a/numbench/main.py
+++ b/numbench/main.py
@@ -86,7 +86,9 @@ def tests_from_input(input):
# if @file: read bash script and set env
elif var[0] == '@':
- fileenv = readEnvFile(pjoin(cfg.curdir, var[1:]))
+ fileenvNew = readEnvFile(pjoin(cfg.curdir, var[1:]))
+ fileenv = dict( fileenv.items() + fileenvNew.items() )
+ del fileenvNew
# Otherwise, assume key=value syntax
else:
reply other threads:[~2011-08-19 11:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=956c17a127d65428d8cece41844c07fa3833f585.spiros@gentoo \
--to=andyspiros@gmail.com \
--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