I believe the situation that is causing the error has to do with GCC's
FORTIFY_SOURCE. I'm building under CentOS 5.2 using the 1.3 src.rpm
available on the website:
% gcc -DHAVE_CONFIG_H -I. -I.. -I../tools/opari/lib -I../extlib/otf/otflib
-I../extlib/otf/otflib -D_GNU_SOURCE
Sorry, I have searched the whole day for a solution of that problem, but
unfortunately, I'm clueless :-( I cannot say which flag causes the
compile error. Furthermore, I'm also unable to reproduce this error on
some different platforms.
The coding style in the concerned source file looks also not
Is there some code that can be fixed instead? I.e., is this feature
totally incompatible with whatever RPM compiler flags are used, or is
it just some coding style that these particular flags don't like?
On Jan 14, 2009, at 5:05 AM, Matthias Jurenz wrote:
Another workaround should be to
Another workaround should be to disable the I/O tracing feature of VT
by adding the configure option
'--with-contrib-vt-flags=--disable-iotrace'
That will have the effect that the upcoming OMPI-rpm's have no support
for I/O tracing, but in our opinion it is not so bad...
Furthermore, we
I don't want to move changes ( default value of the flag), since there
are important people, for whom it works :)
I also think that this is VT issue, but I guess we are the only one
who experience the errors.
we can now overwrite this params from the environment as a workaround,
Mike comitted
I'm still guessing that this is a distro / compiler issue -- I can
build with the default flags just fine...?
Can you specify what distro / compiler you were using?
Also, if you want to move the changes that have been made to
buildrpm.sh to the v1.3 branch, just file a CMR. That file is
it seems that setting use_default_rpm_opt_flags to 0 solves the problem.
Maybe vt developers should take a look on it.
Lenny.
On Sun, Jan 11, 2009 at 2:40 PM, Jeff Squyres wrote:
> This sounds like a distro/compiler version issue.
>
> Can you narrow down the issue at all?
>
This sounds like a distro/compiler version issue.
Can you narrow down the issue at all?
On Jan 11, 2009, at 3:23 AM, Lenny Verkhovsky wrote:
it doesnt happen if I do autogen, configure and make install,
only when I try to make an rpm from the tar file.
On Thu, Jan 8, 2009 at 9:43 PM, Jeff
it doesnt happen if I do autogen, configure and make install,
only when I try to make an rpm from the tar file.
On Thu, Jan 8, 2009 at 9:43 PM, Jeff Squyres wrote:
> This doesn't happen in a normal build of the same tree?
>
> I ask because both 1.3r20226 builds fine for me
This doesn't happen in a normal build of the same tree?
I ask because both 1.3r20226 builds fine for me manually (i.e., ./
configure;make and buildrpm.sh).
On Jan 8, 2009, at 8:15 AM, Lenny Verkhovsky wrote:
Hi,
I am trying to build rpm from nightly snaposhots of 1.3
with the downloaded
Hi,
I am trying to build rpm from nightly snaposhots of 1.3
with the downloaded buildrpm.sh and ompi.spec file from
http://svn.open-mpi.org/svn/ompi/branches/v1.3/contrib/dist/linux/
I am getting this error
.
Making all in vtlib
make[5]: Entering directory
11 matches
Mail list logo