From: Mike Frysinger <vapier@gentoo.org>
To: Will L Givens <wlgivens@gmail.com>
Cc: 'Matt Turner' <mattst88@gmail.com>,
libc-ports@sourceware.org, linux-alpha@vger.kernel.org
Subject: Re: Build Error with GLIBC-2.11.1
Date: Wed, 17 Mar 2010 19:13:59 -0400 [thread overview]
Message-ID: <201003171914.00585.vapier@gentoo.org> (raw)
In-Reply-To: <00d001cac617$00184b20$0048e160$@com>
[-- Attachment #1: Type: Text/Plain, Size: 908 bytes --]
On Wednesday 17 March 2010 17:15:38 Will L Givens wrote:
> > What's available in the glibc.git and glibc-ports.git trees won't
> > build correctly on alpha without patches. These patches are available
> > in Gentoo and are why sane people use Gentoo on their Alphas.
> >
> > I've wasted a bunch of time in the last week trying to help someone
> > who's too stubborn for his own good to build glibc manually. He never
> > succeeded. There's absolutely no point in trying to help you with
> > this. Sorry.
> >
> > You know the solution.
>
> That's one way to win supporters because we all know EVERYONE wants to run
> Gentoo! And you're right, I do know what to do, GLIBC-2.10, the one you
> didn't help with builds fine *lol* So I guess that makes 2 GLIBC-2.11.1
> Alpha users.
>
> It's a free world
you're right ... and in this free world, you're free to do the work yourself
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-03-17 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 5:26 Build Error with GLIBC-2.11.1 Will L Givens
2010-03-17 15:17 ` Matt Turner
2010-03-17 21:15 ` Will L Givens
2010-03-17 23:13 ` Mike Frysinger [this message]
[not found] ` <00d501cac62a$6d8cf1c0$48a6d540$@com>
2010-03-19 17:12 ` Mike Frysinger
2010-03-19 17:50 ` Will L Givens
2010-03-19 18:10 ` Mike Frysinger
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=201003171914.00585.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=libc-ports@sourceware.org \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=wlgivens@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).