Dear Rolf, I compiled openmpi-trunk with $ ../configure --prefix=/opt/openmpi-trunk --disable-mpi-interface-warning --with-cuda=/opt/cuda And that error is now gone!
Thanks a lot for your assistance, - D. 2012/6/19 Rolf vandeVaart <rvandeva...@nvidia.com> > Dmitry:**** > > ** ** > > It turns out that by default in Open MPI 1.7, configure enables warnings > for deprecated MPI functionality. In Open MPI 1.6, these warnings were > disabled by default.**** > > That explains why you would not see this issue in the earlier versions of > Open MPI.**** > > ** ** > > I assume that gcc must have added support for > __attribute__((__deprecated__)) and then later on > __attribute__((__deprecated__(msg))) and your version of gcc supports both > of these. (My version of gcc, 4.5.1 does not support the msg in the > attribute)**** > > ** ** > > The version of nvcc you have does not support the "msg" argument so > everything blows up.**** > > ** ** > > I suggest you configure with -disable-mpi-interface-warning which will > prevent any of the deprecated attributes from being used and then things > should work fine.**** > > ** ** > > Let me know if this fixes your problem.**** > > ** ** > > Rolf**** > > ** ** > > *From:* users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] *On > Behalf Of *Rolf vandeVaart > *Sent:* Monday, June 18, 2012 11:00 AM > > *To:* Open MPI Users > *Cc:* Олег Рябков > *Subject:* Re: [OMPI users] NVCC mpi.h: error: attribute "__deprecated__" > does not take arguments**** > > ** ** > > Hi Dmitry:**** > > Let me look into this.**** > > ** ** > > Rol*f***** > > ** ** > > *From:* users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] *On > Behalf Of *Dmitry N. Mikushin > *Sent:* Monday, June 18, 2012 10:56 AM > *To:* Open MPI Users > *Cc:* Олег Рябков > *Subject:* Re: [OMPI users] NVCC mpi.h: error: attribute "__deprecated__" > does not take arguments**** > > ** ** > > Yeah, definitely. Thank you, Jeff. > > - D.**** > > 2012/6/18 Jeff Squyres <jsquy...@cisco.com>**** > > On Jun 18, 2012, at 10:41 AM, Dmitry N. Mikushin wrote: > > > No, I'm configuring with gcc, and for openmpi-1.6 it works with nvcc > without a problem.**** > > Then I think Rolf (from Nvidia) should figure this out; I don't have > access to nvcc. :-)**** > > > > Actually, nvcc always meant to be more or less compatible with gcc, as > far as I know. I'm guessing in case of trunk nvcc is the source of the > issue. > > > > And with ./configure CC=nvcc ....etc. it won't build: > > > /home/dmikushin/forge/openmpi-trunk/opal/mca/event/libevent2019/libevent/include/event2/util.h:126:2: > error: #error "No way to define ev_uint64_t"**** > > You should complain to Nvidia about that.**** > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users**** > > ** ** > ------------------------------ > > This email message is for the sole use of the intended recipient(s) and > may contain confidential information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. **** > ------------------------------ > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >
