All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Sascha Ziemann <ceving@gmail.com>, git@vger.kernel.org
Subject: Re: How to compile without iconv?
Date: Tue, 09 Jun 2015 20:46:18 +0200	[thread overview]
Message-ID: <5577347A.5080107@web.de> (raw)
In-Reply-To: <CAGUt3y4RgtkP35XstHGQ=T3zkb_akZSRS=q227wMehVzmu9MDA@mail.gmail.com>

On 2015-06-09 16.07, Sascha Ziemann wrote:
> I tried to compile git 2.4.3 on Solaris 10. I used the following configuration:
> 
> $ ./configure --without-iconv
> 
> $ grep -i iconv config.status
> ac_cs_config="'--without-iconv'"
>   set X /bin/bash './configure'  '--without-iconv'
> $ac_configure_extra_args --no-create --no-recursion
> OLD_ICONV=UnfortunatelyYes
> 
> But when I try to compile it, I get an error that libiconv is missing:
> 
>     LINK git-credential-store
> Undefined                       first referenced
>  symbol                             in file
> libintl_gettext                     libgit.a(lockfile.o)
> libiconv_close                      libgit.a(utf8.o)
> libiconv_open                       libgit.a(utf8.o)
> libintl_ngettext                    libgit.a(date.o)
> libiconv                            libgit.a(utf8.o)
> ld: fatal: symbol referencing errors. No output written to git-credential-store
> collect2: ld returned 1 exit status
> gmake: *** [git-credential-store] Error 1
> 
> How can I work around this?

It seems that you need to switch of gettext as well.
(Somewhat untested, I don't have Solaris)
What happens if you run the default Makefile (without configure)

NO_ICONV=t NO_GETTEXT=t make

      reply	other threads:[~2015-06-09 18:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 14:07 How to compile without iconv? Sascha Ziemann
2015-06-09 18:46 ` Torsten Bögershausen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5577347A.5080107@web.de \
    --to=tboegi@web.de \
    --cc=ceving@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.