From: Bill Nottingham <notting@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: static gcc from toolchain: howto?
Date: Wed, 06 Dec 2000 15:24:49 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205797@msgid-missing> (raw)
Francis Galiegue (fg@mandrakesoft.com) said:
> I've been trying for two days now to compile a static gcc (and possibly other
> tools too) but failed. When I try and set LDFLAGS or LDFLAGS_FOR_TARGET to
> -static, I get lots of multiple to _nl_* stuff, hence only i18n stuff... And I
> cannot seem to get out of it, no matter how I try. There's no static-* target
> either.
>
> What is the solution? Or is there a static toolchain binary tree to be d/led
> somewhere?
configure --disable-nls works for me.
Bill
reply other threads:[~2000-12-06 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-105590678205797@msgid-missing \
--to=notting@redhat.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 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.