Hi,
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,
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.
On Sep 3, 2013, at 3:49 PM, Jeff Squyres (jsquyres) jsquy...@cisco.com
wrote:
On Sep 3, 2013, at 6:45 PM, FabrÃcio Zimmerer Murta fabri...@familiamurta.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
How about sym linking the source file? Then you would only need a single
Makefile.am; you can use different flags depending on which source file you
compile.
While somewhat gross, it's not totally disgusting, and it should work to the
same effect...?
On Aug 30, 2013, at 4:16 AM, Bert Wesarg
, 2013 4:24 pm
To: Open MPI Developers
Cc: Automake List
Subject: Re: [OMPI devel] GNU Automake 1.14 released
How about sym linking the source file? Then you would only need a single
Makefile.am; you can use different flags depending on which source file you
compile.
While somewhat gross, it's
Jeff Squyres (jsquyres) jsquy...@cisco.com writes:
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.
Hmm, how about just cp ...? :]
-miles
--
80% of success is just
On 09/04/2013 09:10 AM, Miles Bader wrote:
Jeff Squyres (jsquyres)jsquy...@cisco.com writes:
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.
Hmm, how about just cp
