On Tuesday 03 September 2013 16:01:30 Ralph Castain wrote:
> I still don't see an issue with just detecting the version of automake being
> used, and setting a conditional that indicates whether or not to use
> explicitly include the subdir. Seems like a pretty trivial solution.
Ralph, sorry, we don't understand your proposal. The warnings will be generated at automake time. An AM_CONDITIONAL wont help us here.
> On Sep 3, 2013, at 3:49 PM, "Jeff Squyres (jsquyres)" <email@example.com> wrote:
> > On Sep 3, 2013, at 6:45 PM, FabrÝcio Zimmerer Murta <firstname.lastname@example.org> wrote:
> >> I think autotools has a concept of disallowing symlinks as it seems
> >> symlinks can't be done in a portable way, and the goal of autotools is
> >> making projects portable.
> >> Well, if the autotools user feels like using symlinks, then it must be
> >> expected to break portability wherever you take your autoconfiscated
> >> code to. A choice to the user. Maybe in the case, as the project is
> >> bound to specific compilers, it would not be a problem to loose
> >> portability a bit more by considering symbolic linking around.>
> > Fair enough.
> > We've been using sym links in the OMPI project for years in order to
> > compile a series of .c files in 2 different ways. It's portable to all
> > the places that we need/want it.
Jeff, I think you mean the $(LN_S) loops for the PMPI interface. We will have a look into this. Thanks.
> devel mailing list
Technische Universitńt Dresden
Center for Information Services and High Performance Computing (ZIH)
01062 Dresden, Germany
Phone: +49 (351) 463-31945
Fax: +49 (351) 463-37773