Linux IA64 platform development
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] static gcc from toolchain: howto?
Date: Wed, 06 Dec 2000 20:16:06 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205799@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205796@msgid-missing>

> When I try and set LDFLAGS or LDFLAGS_FOR_TARGET to
>-static, I get lots of multiple to _nl_* stuff, hence only i18n stuff...

What I used to do was just replace the intl/libintl.a files with empty
archives.

cd intl
rm libintl.a
ar rc libintl.a
cd ..

There are two of these directories, intl, and gcc/intl.  I think this is the
easiest solution.

The real solution is to build and install gettext before running configure.
autoconf checks to see if the host has i18n support by trying to run xgettext.
If the program isn't there, then it assumes that we need to build our own
i18n library.  If you link against a shared glibc, this isn't a problem.
If you link against a static glibc, then you get the multiple definitions
link error.  I suppose if you don't have gcc yet, then building gettext might
be a problem.  So you will need to use a workaround once to bootstrap.

Bill Nottingham's suggestion of using --disable-nls should work too, but you
have to remember to use it before running configure.

Jim


      reply	other threads:[~2000-12-06 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 12:18 [Linux-ia64] static gcc from toolchain: howto? Francis Galiegue
2000-12-06 20:16 ` Jim Wilson [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=marc-linux-ia64-105590678205799@msgid-missing \
    --to=wilson@cygnus.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox