hey again, One quick follow-up, as things are still misbehaving...
While removing --enable-picky in the ompi_configure_arguments got MTT to compile the nightly tarball, no MPI program succeeds (both in MTT and outside) for any BTL included in the nightly tarball when ran on FreeBSD 7. I did a quick investigation and it appears as if I'm arriving at the same thing that Karol did in the Apr 5th email in this thread... Things hang on the call to kevent on line 177 of opal/event/kqueue.c . Jeff had replied asking if Karol had only ran locally, citing past problems he'd seen with kevent running locally. I tried also running on a remote machine, and it hung in the same way. George mentioned he had done a fix for an OS X issue recently.... just curious but did you guys (or anyone else) ever get a chance to cycle back to this? Thanks! brad On Tue, Apr 29, 2008 at 4:45 PM, Brad Penoff <pen...@cs.ubc.ca> wrote: > hey all, > > I was just configuring MTT to run some multihost tests on FreeBSD 7 > and I came across this same error you guys were, using the > openmpi-1.3a1r18325.tar.gz trunk nightly tarball : > > kqueue.c:165: error: implicit declaration of function 'openpty' > > However, this error seems to only come up if I use --enable-picky to > configure. Getting rid of --enable-picky results in a successful > compilation. Any idea why that is? Should this be fixed in the long > term? > > For now, I'm just adjusting my MTT runs to not have --enable-picky in > the ompi_configure_arguments... > > brad > > > 2008/4/11 George Bosilca <bosi...@eecs.utk.edu>: > > > > That's good that you guys revive this thread, I almost forget about it. > > > > The code you're referring, is not part of the libevent. It was one of my > > "fixes" around for problem on OS X (where kevent is not able to work nicely > > with pty). It works on MAC as the code trigger an error so there is no need > > for the timeout ... I'll make the corrections over the weekend. > > > > Thanks, > > george. > > > > > > > > On Apr 11, 2008, at 7:39 PM, Karol Mroz wrote: > > > > > Hi, Jeff... > > > > > > This test was performed locally, yes. I'm short on machines at the moment > > to perform any proper distributed tests. > > > > > > -- > > > Karol > > > > > > -----Original Message----- > > > From: Jeff Squyres <jsquy...@cisco.com> > > > > > > Date: Fri, 11 Apr 2008 16:36:33 > > > To:Open MPI Developers <de...@open-mpi.org> > > > Subject: Re: [OMPI devel] Build failure on FreeBSD 7 > > > > > > > > > This may depend on how you ran the app on FreeBSD -- did you run on > > > the localhost only? > > > > > > We have/had a problem when running locally with regards to kevent -- > > > I'm not 100% sure if we've fixed it yet. Let me check... > > > > > > > > > On Apr 5, 2008, at 1:53 AM, Karol Mroz wrote: > > > > > > > After digging a little deeper, it turns out that the kevent() call in > > > > opal/event/kquene.c: > > > > if (kevent(kq, > > > > kqueueop->changes, 1, kqueueop->events, NEVENT, NULL) != > > > > 1 || > > > > (int)kqueueop->events[0].ident != master || > > > > kqueueop->events[0].flags != EV_ERROR) { > > > > > > > > seems to hang in freebsd 7. Changing the NULL parameter to, lets say > > > > 1000, causes the function to return and print out the error message: > > > > > > > > event_warn("%s: detected broken kqueue (failed delete); not > > using > > > > error %d (%s)", __func__, errno, strerror(errno)); > > > > > > > > The simple non-blocking send/recv app used to test this then runs to > > > > completion. Compiling OpenMPI on linux and running this same app > > > > produces no errors. > > > > > > > > Any ideas? > > > > > > > > Thanks. > > > > -- > > > > Karol > > > > > > > > > > > > > > > > _______________________________________________ > > > > devel mailing list > > > > de...@open-mpi.org > > > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > > > > > > > > > > > -- > > > Jeff Squyres > > > Cisco Systems > > > > > > _______________________________________________ > > > devel mailing list > > > de...@open-mpi.org > > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > > > > _______________________________________________ > > > devel mailing list > > > de...@open-mpi.org > > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > > > > > > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > >