git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Is NO_ICONV misnamed or is it broken?

From
Mahmoud Al-Qudsi <mqudsi@neosmart.net>
Date
Jun 14, 2018, 22:47 UTC
Message-ID
<CACcTrKePbgyCbXneN5NZ+cS-tiDyYe_dkdwttXpP0CUeEicvHw@mail.gmail.com>
Hello list,

With regards to the Makefile define/variable `NO_ICONV` - the Makefile comments imply that it should be used if "your libc doesn't properly support iconv," which could mean anything from "a patch will be applied" to "iconv won't be used."

Based off the name of the varibale, the assumption is that iconv is an optional dependency that can be omitted if compiled with NO_ICONV. However, in practice attempting to compile git with `make ... NO_ICONV=1` and libiconv not installed results in linker errors as follows:

```
~> make clean
# omitted
~> make NO_ICONV=1
# ommitted
    LINK git-credential-store
/usr/bin/ld: cannot find -liconv
cc: error: linker command failed with exit code 1 (use -v to see invocation)
gmake: *** [Makefile:2327: git-credential-store] Error 1
```

Am I misunderstanding the intended behavior when NO_ICONV is defined (i.e. it does not remove the dependency on libiconv) or is this a bug and iconv should not, in fact, be required?

Many thanks,

Mahmoud Al-Qudsi NeoSmart Technologies

Next: Eric Sunshine
Message 1 of 15 in “Is NO_ICONV misnamed or is it broken?”
  1. Mahmoud Al-QudsiJun 14, 2018
  2. Makefile: make NO_ICONV really mean "no iconv"Eric Sunshine, Jun 15, 2018
  3. Jeff KingJun 15, 2018
  4. Eric SunshineJun 15, 2018
  5. Jeff KingJun 15, 2018
  6. Simon RuderichJun 15, 2018
  7. Eric SunshineJun 15, 2018
  8. Kaartic SivaraamJun 17, 2018
  9. Eric SunshineJun 17, 2018
  10. Doc/SubmittingPatches: re-phrashing a sentence about alternate solutions (was Re: [PATCH] Makefile: make NO_ICONV really mean "no iconv")Kaartic Sivaraam, Jun 17, 2018
  11. Jeff KingJun 18, 2018
  12. Junio C HamanoJun 18, 2018
  13. Mahmoud Al-QudsiJun 15, 2018
  14. Christian CouderJun 17, 2018
  15. Eric SunshineJun 17, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.