Excellent! Sorry it took so long to resolve this.
We could put in a few fixes to protect against this specific error
(where we call `which $CC|$CXX`), but I'm not sure if there are other
places in the configure process that rely on `foo` to output only 1
line of data. So I'm not sure that it would be worth it.
Specifically, I think that classifying this problem as a "user
configuration error" is acceptable. I'll add this particular issue
to the FAQ, though, because it was sufficiently weird/non-obvious
what the real problem was so that it will be google-able.
FWIW, shouldn't DISPLAY stuff be set in .login (vs. .tcshrc)?
On Oct 9, 2007, at 8:44 AM, Michael Clover wrote:
Jeff,
as it turned out, my .tcshrc file did output "DISPLAY known"... I
had logic to set DISPLAY if it was undefined:
if ( ! $?DISPLAY ) then
if ( ! $?SSH_CLIENT ) then
if ( "$OS" == "darwin") then
# ........... irrelevant
else
echo "no environment variable to capture your IP from"
set w_data = $user
setenv DISPLAY ${w_data}:0.0
endif
else
set whom = `echo $SSH_CLIENT `
if ( $?whom ) then
set i_am = `echo $whom[1] | sed -e "s/::ffff:128/128/"`
setenv DISPLAY ${i_am}:0.0
echo " DISPLAY set from SSH_CLIENT"
endif
endif
else
echo " DISPLAY known"
endif
I have commented out the echo of "display known", and now
openmpi-1.2.4 makes just fine. Furthermore, openmpi-1.2.3 no longer
generates the unterminated newlines for sed either, and also makes
correctly. I must have mistyped something when I grep'ed for
"display" or "known" before my reply to Reuti, since I didn't find it
until your question. thanks for all the help.
Michael Clover
mclo...@san.rr.com
On Oct 8, 2007, at 11:09 , users-requ...@open-mpi.org wrote:
On Oct 8, 2007, at 9:00 , users-requ...@open-mpi.org wrote:
------------------------------
Message: 5
Date: Tue, 9 Oct 2007 08:08:23 +0200
From: Jeff Squyres <jsquy...@cisco.com>
Subject: Re: [OMPI users] ompi-1.2.4 fails to make on iMac (10.4.10)
To: Open MPI Users <us...@open-mpi.org>
Message-ID: <897eb321-9a89-4d8b-8b19-d53225573...@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
From the files you attached, I see the following in config.log:
OMPI_CC_ABSOLUTE=' DISPLAY known
and several lines later:
OMPI_CXX_ABSOLUTE=' DISPLAY known
But in Makefile, I see this bogus 2-line value (same as you noted):
OMPI_CC_ABSOLUTE = DISPLAY known
/usr/bin/gcc
and several lines later:
OMPI_CXX_ABSOLUTE = DISPLAY known
/usr/bin/g++
Note that we set these two values in configure with the following
commands:
OMPI_CC_ABSOLUTE="`which $CC`"
OMPI_CXX_ABSOLUTE="`which $CXX`"
So I *suspect* that the bogus values in config.status are totally
hosing you when trying to create all the other files -- the version
of "sed" is a red herring.
What exactly is your output when you run "which gcc" and "which g+
+"? We are blindly taking the whole value -- mainly because I've
never seen "which foo" give more than one line on stdout. ;-)
What *could* be happening is that your shell startup files are
generating some output (e.g., "DISPLAY known") and that's being
output before "which foo" is run because of the `` usage. Do your
shell startup files emit "DISPLAY known" when you start up?
------------------------------
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
End of users Digest, Vol 713, Issue 1
*************************************
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
Cisco Systems
