Good morning Gilles and Franz-Joseph. Gilles,
You're absolutely right...compilation is not actually at fault. The report I received stated that the removal of __malloc_initialize_hook from glibc2.24 was causing a build failure. Apparently I took the report too literally, and in order to rush a fix so as not to gate glibc, well... :/ Now that I've looked more closely at the original logs, it's nothing more than a packaging issue. A different subset of files are included, nothing more. So let me apologize for the false alarm and the wasted time. Mea culpa. I still want to get 2.0.x into Tumbleweed. However, this can now be done at a normal pace. Regards, Karol On Wed, Aug 24, 2016 at 11:53 PM, Gilles Gouaillardet <gil...@rist.or.jp> wrote: > Karol, > > > i was able to build openmpi 1.10.3 and run simple programs on tumbleweed > with updated glibc (2.24-436.59) i downloaded from > > http://download.opensuse.org/repositories/Base:/System/ > openSUSE_Factory/x86_64/ > > > would you mind describing the issue you faced with the updated glibc and > openmpi 1.10.3 ? > > > Cheers, > > > Gilles > > On 8/25/2016 11:56 AM, Gilles Gouaillardet wrote: > > Karol, > > > is there any place i can download glibc 2.24 for tumbleweed ? > > > i'd like to have a look at what is going wrong with openmpi 1.10 > > > Cheers, > > > Gilles > > On 8/25/2016 10:24 AM, Karol Mroz wrote: > > Greetings! > > I would like to upgrade our (openSUSE Tumbleweed) version of Open MPI from > 1.10.3 to the shiny new 2.0.0 :) This is motivated by a number of factors, > including an upgrade to glibc2.24 which breaks our current build of Open > MPI. I thought it a great time to push out a new version :D > > The current issue I'm running into when building our RPMs, is the apparent > disappearance of all -vt related binaries and files. Looking over the > configure script in 2.0.0 and some logs in ompi-release, am I right in > assuming that vampirtrace has been completely removed? I can no longer > find, for example, the --disable-vt option in configure, and my RPM logs > complain of missing mpicc-vt et al. > > Any insight would be a great help! > > Thanks in advance, > Karol > > > _______________________________________________ > devel mailing > listde...@lists.open-mpi.orghttps://rfd.newmexicoconsortium.org/mailman/listinfo/devel > > > > > _______________________________________________ > devel mailing > listde...@lists.open-mpi.orghttps://rfd.newmexicoconsortium.org/mailman/listinfo/devel > > > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
