Linkage failing on OS/X Lion

[arikfr]

Linkage failing on OS/X Lion

[alloy]

It’s probably using an iconv that you’ve installed which has not been built for x86_64. Can you find the iconv being used and check it with file? In my case it’s the system version:

% file /usr/lib/libiconv.dylib
/usr/lib/libiconv.dylib: Mach-O universal binary with 3 architectures
/usr/lib/libiconv.dylib (for architecture x86_64):  Mach-O 64-bit dynamically linked shared library x86_64
/usr/lib/libiconv.dylib (for architecture i386):    Mach-O dynamically linked shared library i386
/usr/lib/libiconv.dylib (for architecture ppc7400): Mach-O dynamically linked shared library ppc

Alternatively, you can download a build: https://github.com/alloy/macvim/downloads

[arikfr]

I'm not sure which libiconv.dylib it uses, but if it uses the one in /usr/lib then my results are similar to yours:

$ file /usr/lib/libiconv.dylib
/usr/lib/libiconv.dylib: Mach-O universal binary with 2 architectures
/usr/lib/libiconv.dylib (for architecture x86_64):  Mach-O 64-bit dynamically linked shared library x86_64
/usr/lib/libiconv.dylib (for architecture i386):    Mach-O dynamically linked shared library i386```
How can I tell which one it really uses?

For some reason I was under the impression that there are no builds for downloads. Will try it now. Thanks.

[alloy]

In the command it includes these options: -L/opt/local/lib -L/usr/local/lib, that’s where I’m guessing you might find it.

[arikfr]

In both of these paths the libiconv file is compiled for 64bit. Is there a way to make the linkage process more verbose and print out the file it tries to link?

[alloy]

Hmm, sorry, I’m not familiar enough with those compiler options :/ Another thing you can try is to use mdfind to look for potential other installations of the lib, or otherwise grab the latest build from: https://github.com/alloy/macvim/downloads

[arikfr]

All the version that I found via mdfind (except that ones of the iPhone simulator) are 64bit. I'm giving up at this point -- I will just use your build.

Yesterday I had performance issues with the latest build, but the build 250720112118 seems to work fine. I will try to work with it for a day, and if all goes ok I will try the latest again.

Thank you!

[alloy]

What kind of performance issues were you running into? Because the 250720112118 build is really outdated compared to upstream. It might be useful to see if you are experiencing the same performance issues with an upstream build.

[arikfr]

Just to clarify, I had the performance issues with the 020920111108 build. Everything was slow and after I closed MacVim, there were still vim processes running in the background using 60% CPU.

So far the 250720112118 build was running ok, so I will give the 020920111108 build second chance.