Re: AX_CREATE_PKGCONFIG_INFO and hardcoded paths
On 03/27/2013 06:41 AM, LRN wrote: I've been cross-compiling cloog, and noticed that cloog creates a .pc file by simply doing: PACKAGE_NAME=cloog-isl PACKAGE_CFLAGS=-DCLOOG_INT_GMP=1 AX_CREATE_PKGCONFIG_INFO Is this an AX_CREATE_PKGCONFIG_INFO feature, or cloog does something wrong? AX_CREATE_PKGCONFIG_INFO is not maintained by autoconf; perhaps you'll get better answers to your questions by asking on the Autoconf Archive mailing list: autoconf-archive-maintain...@gnu.org -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
Re: AX_CREATE_PKGCONFIG_INFO and hardcoded paths
LRN lrn1...@gmail.com writes: However, -L/root/lib and -I/root/include are hardcoded, and thus are completely wrong (and potentially dangerous, if the system where cloog is deployed has /root/include and/or /root/lib directories. Is this an AX_CREATE_PKGCONFIG_INFO feature, or cloog does something wrong? The various versions of AX_CREATE_PKGCONFIG_INFO that I've seen all do things that I consider rather dodgy, such as putting the entire contents of CFLAGS into the pkgconfig file (including any user-supplied CFLAGS at configure time and including optimization flags). I suspect this is similar. I'm not sure if there's a newer version of the macro available that's less aggressive about copying the *entire* build configuration into the pkgconfig file, but in the meantime I've preferred to construct my pkgconfig files using sed from Makefile.am so that I have more control over exactly what goes into them. -- Russ Allbery (r...@stanford.edu) http://www.eyrie.org/~eagle/ ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
Re: AX_CREATE_PKGCONFIG_INFO and hardcoded paths
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.03.2013 20:12, Eric Blake wrote: On 03/27/2013 06:41 AM, LRN wrote: I've been cross-compiling cloog, and noticed that cloog creates a .pc file by simply doing: PACKAGE_NAME=cloog-isl PACKAGE_CFLAGS=-DCLOOG_INT_GMP=1 AX_CREATE_PKGCONFIG_INFO Is this an AX_CREATE_PKGCONFIG_INFO feature, or cloog does something wrong? AX_CREATE_PKGCONFIG_INFO is not maintained by autoconf; perhaps you'll get better answers to your questions by asking on the Autoconf Archive mailing list: autoconf-archive-maintain...@gnu.org I've decided to send the message to autoconf list because i found [1], where people discussed this very macro. [1] http://lists.gnu.org/archive/html/autoconf/2012-09/msg00048.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRUyffAAoJEOs4Jb6SI2CwqNsIAIY0w2BYb3zeSOtgkRfVQpbK GTmWnotDupivAciuzj+VzSces5xivecv6YOCovKGgIRCht2PU+MMK2WB3YR95ROd cVdT1RxpigdOw3SUkTQjL49l+swcVyqX5KKYSx+JFvkir5iORjZDHd64vVrMqfzt SfsBaJB4ynC5IkX5HLce8iOayz+E85K6TVOFYKjsf2jhIEwPIHM22h8Lb8piJbKC wJQTzprIyzJCdLqoFN5gpfhgrIgbHJgRJouKw87evVdgOj/TgBzl7xMpXo9UZtzl AEs/pqUkNF5jxB0ylea24rCAe0M2SN4cQM+ksZwWDUzxy8bbawUMlsg2h8Ox1NA= =xnbl -END PGP SIGNATURE- ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
