autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AC_PROG_CC_C99 and AC_OPENMP


From: Joel J. Adamson
Subject: Re: AC_PROG_CC_C99 and AC_OPENMP
Date: Fri, 07 May 2010 15:51:44 -0400

Joel J. Adamson <address@hidden> wrote:

> William Pursell <address@hidden> wrote:
> 
> > Joel J. Adamson wrote:
> > > Ralf Wildenhues <address@hidden> wrote:
> > 
> > >> If you don't need to work with Autoconf < 2.62, I suggest you add an
> > >>   AC_PREREQ([2.62])
> > > 
> > > I had it, and then I discovered that the Beowulf cluster (emerald) at
> > > the university here has version 2.59.
> > 
> > I don't understand how that's an issue.  If you have write permission
> > on a directory on the box in which you are doing development (and I
> > can't see how one could do anything that would be called 'development'
> > without it), then you can install modern autoconf and use it.
> 
> That's a good point; I hadn't thought about it that (remarkably logical)
> way.

Okay Bill, I've thought about it a little more and your point still
stands, but here are two problems:

1) It adds another step in deploying development code on the cluster
(not a big problem)

2) If I'm developing on the cluster with Ancient Autoconf and I need to
fix *other* portability issues (related to the package maintainer's
mysterious inability to update packages) then I can't test and edit my
code on the cluster where I need to fix those issues.  Not without
introducing another few inconvenient steps to the process.

Thanks again,

Joel
-- 
Joel J. Adamson
Servedio Lab
University of North Carolina at Chapel Hill

FSF Member #8164
http://www.unc.edu/~adamsonj

Attachment: pgpPFEQ5lqBXb.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]