Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script does not work for non-English locales #2

Open
antoinemine opened this issue Feb 10, 2024 · 1 comment
Open

Script does not work for non-English locales #2

antoinemine opened this issue Feb 10, 2024 · 1 comment

Comments

@antoinemine
Copy link

The sed commands in lookup_lib assume that the output of the compiler are in English. The script fails for other locales as it cannot extract the library path.

For instance, in a FR locale, gcc -print-search-dirs will give:

installés: /usr/lib/gcc/x86_64-pc-linux-gnu/13/
programmes: =/usr/libexec/gcc/x86_64-pc-linux-gnu/13/:/usr/libexec/gcc/x86_64-pc-linux-gnu/13/:/usr/libexec/gcc/x86_64-pc-linux-gnu/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/:/usr/lib/gcc/x86_64-pc-linux-gnu/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu/13/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/
bibliothèques: =/usr/lib/gcc/x86_64-pc-linux-gnu/13/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/lib/x86_64-pc-linux-gnu/13/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/lib/../lib64/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../x86_64-pc-linux-gnu/13/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../lib64/:/lib/x86_64-pc-linux-gnu/13/:/lib/../lib64/:/usr/lib/x86_64-pc-linux-gnu/13/:/usr/lib/../lib64/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/lib/:/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../:/lib/:/usr/lib/

This may be related to #1 as the visible result is the same: include file found but library file not found.

Temporary work-around is LANG=C opam install mlgmpidl.

@nberth
Copy link
Owner

nberth commented Feb 11, 2024

Many thanks for the issue and suggested workaround. I'll address it as soon as I come back from holidays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants