Hi,

When i try to install a software, there are few packages i want, and few that i dont want to include. After looking into the ./configure file, got an idea of how to specify if a package should be included or not.

The command that i use to configure is,
$./configure --with-mpiCC=yes --without-g++
This gives out an error saying that the package g++ was not found. But the command i use to compile a c++ program is
$g++ -o filename filename.cpp, if this is the case, how does it say that the package is missing? but when i say $g++ -v it gives out the version number of gcc!
for this when i just give $./configure --with-mpiCC=yes --without-gcc
once again g++ is included for configuring! is there any solution for this?

PLease let me know! i've copy pasted a part of the configure file for refernece....

This is from my ./configure file
Optional Features:
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-shared[=PKGS]
build shared libraries [default=yes]
--enable-static[=PKGS]
build static libraries [default=yes]
--enable-fast-install[=PKGS]
optimize for fast installation [default=yes]
--disable-dependency-tracking Speeds up one-time builds
--enable-dependency-tracking Do not reject slow dependency extractors
--disable-libtool-lock avoid locking (might break parallel builds)
--disable-modeleditor disable the modeleditor.
--disable-compiler-extensions
Don't exploit the compiler's special language syntax
and optimizations that are not part of the standard
(such as ISO C++).

Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-gnu-ld assume the C compiler uses GNU ld [default=no]
--with-pic try to use only PIC/non-PIC objects [default=use
both]
--with-tags[=TAGS]
include additional configurations [automatic]
--without-gtk build ecell without gtk library.
--with-boost-root-dir= specify a non-standard root installation directory
for boost library.

Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
headers in a nonstandard directory <include dir>
CPP C preprocessor
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CXXCPP C++ preprocessor
F77 Fortran 77 compiler command
FFLAGS Fortran 77 compiler flags

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.


Thanks,

Nithila.

What is the software you're trying to build? If it's looking for the package for g++ it's probably just looking for the wrong name, the name can differ from distribution to distribution.

Hi,

Thanks for your reply! the software i'm trying to build is ecell. Its a bioinformatics kind of software. It makes use of g++(for c compiler), but i want that to use mpiCC compiler. Specifying it in the command line when configuring does not work, i really dont know what to do.

Thanks,

NG

The last paragraph of the configure script tells you that you can override it's defaults with the environment variables CC, CXX, etc. If you're using bash you can just export those variables and run configure and it should work.

Thanks,

will try doing that

NG.

Hi,

I'm working with a software(e-cell), it is a bioinformatics related software. It is installed on my linux cluster, and it uses gcc as its compiler . It has python script as its front end to bring all the necessary codes together during compilation.

I'm trying to install this software on my cluster with mpiCC as the compiler.
Command i use is,
$./configure CC=mpicc CXX=mpiCC
configure runs without any error.
Next for make i've tried various options, like,
$make
or
$make CC=mpicc CXX=mpiCC
But for all the different options of make that i tried i get the same error. I would like to know if there is any way to overcome this Wno-pmf-converisons error? it is basically used for C++ and gcc supports it, but when i change the software to mpiCC it gives out errors, even though mpi is a wrapper of gcc.

even if i export before configuring i get the same error!!!! is there any other choice for this?

The error is get is

mpiCC -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../.. -I/usr/include -I/workx5/ecell3 -I../../libltdl -g -Wno-pmf-conversions -g -Wno-pmf-conversions -c libecs.cpp -DPIC -o .libs/libecs.o
pgCC-Warning-Unknown switch: -Wno-pmf-conversions
pgCC-Warning-Unknown switch: -Wno-pmf-conversions
"Defs.hpp", line 427: error: identifier "INFINITY" is undefined
const Real INF( INFINITY );
^
"Defs.hpp", line 444: warning: type qualifier on return type is meaningless
inline const Real FMA( const Real a, const Real b, const Real c )
^
"libecs.hpp", line 55: warning: type qualifier on return type is meaningless
inline const int getMajorVersion()
^
"libecs.hpp", line 60: warning: type qualifier on return type is meaningless
inline const int getMinorVersion()
^
"libecs.hpp", line 65: warning: type qualifier on return type is meaningless
inline const int getMicroVersion()
^
1 error detected in the compilation of "libecs.cpp".
make[5]: *** [libecs.lo] Error 1
make[5]: Leaving directory `/workx5/ecell3/ecell/libecs'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/workx5/ecell3/ecell/libecs'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/workx5/ecell3/ecell'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/workx5/ecell3/ecell'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/workx5/ecell3'
make: *** [all] Error 2
[root@master ecell3]#

Please let me know where i'm goign wrong.

Thanks,
NG.