[#3054] Problem in configure

Voir les outils de suivi | Bugs | Télécharger .csv | Nouveau | Surveiller

Date:
03/09/2013 13:14
Priorité:
3
État:
Open
Proposée par:
Nobody
Confié à:
Nobody (None)
Resolution:
None
Group:
None
Category:
None
Status:
Open
Résumé:
Problem in configure

Description détaillée
Anonymous message posted by geertjan.bex@uhasselt.be

Dear,

Thanks for your efforts making GMP available to R.

Our team manages an HPC cluster, and quite a number of our researchers use R. In such an environment, it is common practice to make multiple versions of the same softtware package available, and this is also the case for R.
In order to do this, however, the software packages are not installed in the default directories (obviously, versions would clash). This also implies that when software is build, the build process should not assume that supporting libraries and header files are in standard locations such as /usr/local/lib and /usr/local/include. Usually, this is taken care of by simply setting CPPFLAGS and LDFLAGS to the paths corresponding to desired version before doing a configure (or, in R, an install.packages(...)).

However, your configure script seems to ignore CPPFLAGS and LDFLAGS, which is not really the convention. It would be nice if you could align gmp's configure script with autotools' best practices.

Many thanks, best regards, Geert Jan Bex

Ajouter un commentaire: Notepad

Commentaires

Aucun commentaire n'a été posté.

Fichiers joints:

Changements:

Champ Ancienne valeur Date Par
status_idDeleted26/11/2014 09:41jasson
close_date26/11/2014 09:4026/11/2014 09:41jasson
detailsAnonymous message posted by geertjan.bex@uhasselt.be Dear, Thanks for your efforts making GMP available to R. Our team manages an HPC cluster, and quite a number of our researchers use R. In such an environment, it is common practice to make multiple versions of the same softtware package available, and this is also the case for R. In order to do this, however, the software packages are not installed in the default directories (obviously, versions would clash). This also implies that when software is build, the build process should not assume that supporting libraries and header files are in standard locations such as /usr/local/lib and /usr/local/include. Usually, this is taken care of by simply setting CPPFLAGS and LDFLAGS to the paths corresponding to desired version before doing a configure (or, in R, an install.packages(...)). However, your configure script seems to ignore CPPFLAGS and LDFLAGS, which is not really the convention. It would be nice if you could align gmp's configure script with autotools' best practices. Many thanks, best regards, Geert Jan Bex 26/11/2014 09:41jasson
status_idOpen26/11/2014 09:40jasson
close_dateNone26/11/2014 09:40jasson
Powered By FusionForge