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

[Bug] iconv dependency needs a better configuration on some systems #513

Open
wenzeslaus opened this issue Apr 16, 2020 · 0 comments
Open
Labels
bug Something isn't working
Milestone

Comments

@wenzeslaus
Copy link
Member

Describe the bug
When compiling in some environments such conda (where iconv is installed through conda, not in the system) and at least some old FreeBSD, compilation fails.

To Reproduce
You need a system with special iconv or perhaps no iconv. I don't have any instructions to do that at this point.

Expected behavior
If the automatic detection fails, there should be way in ./configure to specify include and library paths for iconv as well as a name of the library itself. It should be also possible to disable inconv completely like other dependencies.

System description (please complete the following information):

  • CentOS Linux release 7.7.1908 (Core) inside conda, perhaps FreeBSD
  • master or 7.8 branch

Additional context
GRASS compiles and works fine with manually disabled iconv by setting #define HAVE_ICONV_H 0 in include/config.h (220) after ./configure.

Given the large number of dependencies, I think it would not be additional burden if the automatic search for iconv would be disabled and explicit settings would be required for more cases than now, but I don't know how this would play out with the iconv in libc.

According to @metzm and @glynnc the problem is that in the configure script, the header checks and the library checks are disconnected (see links above for details).

This is something to keep in mind for #348 (CMake).

@wenzeslaus wenzeslaus added the bug Something isn't working label Apr 16, 2020
@wenzeslaus wenzeslaus added this to the 8.4.0 milestone Feb 17, 2023
@neteler neteler modified the milestones: 8.4.0, 8.4.1 Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants