libiconv linker errors

[Uncommon]

I'm synced to c2d3af2 (current master), and I've run the bootstrap script and tried cleaning, but I always get these linker errors when building the framework target:

Undefined symbols for architecture x86_64:
  "_libiconv", referenced from:
      _git_path_iconv in libgit2.a(path.c.o)
  "_libiconv_close", referenced from:
      _git_path_iconv_clear in libgit2.a(path.c.o)
  "_libiconv_open", referenced from:
      _git_path_iconv_init_precompose in libgit2.a(path.c.o)

[arrbee]

Do you happen to have iconv installed via MacPorts or another alternative version of iconv?

[Uncommon]

Isn't it a standard library? I haven't installed it explicitly.

[arrbee]

It is. One common source of problems is for people who are not using the standard version. What version of OS X are you running?

[arrbee]

Oh, and are you using MacPorts even if you didn't install it explicitly?

[Uncommon]

I've never used MacPorts. I'm on OS X 10.9.2.

[Uncommon]

The way the Objective Git framework target is set up, it's linked using the linker build phase (rather than a linker flag), using libiconv.dylib as referenced in the project, which according to Xcode is coming from the 10.9 SDK.

[Uncommon]

Also, Xcode 5.1.1.

[jspahrsummers]

If you remove it from the Link Binaries With Libraries phase, and instead add -liconv to the linker flags, does it work then?

[Uncommon]

Nope, same error. I also upgraded to 10.9.3, and tried a fresh clone (not as a submodule of my other repo).

[Uncommon]

Also tried changing the base SDK to 10.8.

[Uncommon]

I reinstalled Xcode in case the library was corrupted. No dice.

https://trac.macports.org/ticket/38851 seemed relevant, but the solution there did not help.

[Uncommon]

I tried making a simple project, adding a call to iconv_open() to the command line tool template, and with the -liconv linker flag it builds just fine.

I noticed that the library search paths for ObjectiveGit are . and External, which doesn't explicitly include /usr/lib, but apparently that doesn't matter; adding it doesn't help. What else could be making the difference?

[jspahrsummers]

Sorry for the radio silence—this is just super weird. We've still never seen this problem, on our machines or CI. 😕

You're using Xcode 5.1, right?

[Uncommon]

Xcode 5.1.1 as noted above.

Yeah, it's pretty weird. I didn't have this problem on the other machines I've worked on.