On Sun, Sep 16, 2012 at 12:46 PM, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: > On Sun, Sep 16, 2012 at 03:19:25AM +0000, ankush_aggar...@dell.com wrote: > >> I have created a GIT repository on Linux 64 bit machine. >> >> When I tried to clone GIT repository on windows 7 machine then I am getting >> below error. >> >> Error: >> git-upload-pack: error while loading shared libraries: libiconv.so.2: cannot >> open shared object file: No such file or directory >> fatal: The remote end hung up unexpectedly >> >> anyone please help me resolve the issue. > See [1] and generally search google for msysgit+libiconv.so.2 as it > contains links to other approaches to working around this problem. > > Note that questions about technical issues with Git for Windows are > better asked on the msysgit mailing list [2] or in the project bug > tracker [3] (after searching both places for the relevant information).
No. This is not a Git for Windows issue. The remote end is the one who isn't able to load libiconv, you can tell from the fact that it complains about "libiconv.so.2", not "libiconv-2.dll", and from the fact that the client informs us that the remote end hung up. Ankush: There's something wrong with the setup on your Linux machine; most likely something related to the library path set up. What protocol are you cloning over? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
