search

apertium / apertium-get

Download and configure an Apertium language pair (along with its monolingual deps) for development
http://wiki.apertium.org/wiki/Apertium-get
GNU General Public License v3.0
3 stars 3 forks source link

Doesn't seem to use correct PKG_CONFIG_PATH on macos #11

Open unhammer opened 3 years ago

unhammer commented 3 years ago

According to mac user, running apertium-get apertium-nno-nob fails on the autogen step with

  configure: error: Package requirements (apertium >= 3.6.0) were not met

while manually running ./autogen.sh works fine.

TinoDidriksen commented 3 years ago

https://apertium.projectjj.com/osx/install-nightly.sh does mention at the end:

echo "You may need to add these to your ~/.profile or session:"
echo 'export PKG_CONFIG_PATH='$WHERE'/share/pkgconfig:${PKG_CONFIG_PATH}'
echo 'export ACLOCAL_PATH='$WHERE'/share/aclocal:${ACLOCAL_PATH}'

Because you can change where the script installs everything, though practically nobody does.

So apertium-get should ideally look for the most recent apertium.pc in the usual locations, then set PKG_CONFIG_PATH and ACLOCAL_PATH accordingly. But a quick'n'dirty implementation can definitely default to /usr/local.

unhammer commented 3 years ago

It seems like the python version stopped using autogen.sh, now it's doing autoreconf

https://github.com/apertium/apertium-get/blob/ea2424ce4f8ef98b37d3005b8ec60a2a3c4184f6/apertium-get.py#L159

(autogen.sh does the PKG_CONFIG_PATH guessing, the old apertium-get script used autogen.sh)