diff options
| author | Geoffrey Oxberry <goxberry@gmail.com> | 2018-01-24 18:48:28 -0800 |
|---|---|---|
| committer | scheibelp <scheibel1@llnl.gov> | 2018-01-24 18:48:28 -0800 |
| commit | e0082e0564ccb1fc838e3248e6d8306132166364 (patch) | |
| tree | 190e544c764c72c1031d1cfc2fbb9d7633da155c /lib | |
| parent | b5daa51c06095fde57ffe05622bb1079355d3b73 (diff) | |
| download | spack-e0082e0564ccb1fc838e3248e6d8306132166364.tar.gz spack-e0082e0564ccb1fc838e3248e6d8306132166364.tar.bz2 spack-e0082e0564ccb1fc838e3248e6d8306132166364.tar.xz spack-e0082e0564ccb1fc838e3248e6d8306132166364.zip | |
libtool: symlink libtool{ize} to glibtool{ize} (#7060)
On Darwin and other BSD systems, the system 'libtool' and 'libtoolize'
are BSD libtool and libtoolize, respectively. Some build systems
require the GNU versions of these commands, so BSD package systems
tend to name the GNU versions 'glibtool' and 'glibtoolize',
respectively, to avoid namespace collisions.
A problem with the current libtool package is that it installs the GNU
libtool commands as 'libtool' and 'libtoolize', respectively, but
build systems on BSD platforms will attempt to run 'glibtool' and
'glibtoolize'. The expedient solution to this problem is to symlink
'libtool' to 'glibtool' and 'libtoolize' to 'glibtoolize', because
attempting to patch the detection logic one build system at a time
seems impractical.
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions