From: "Martin Brulisauer" <martin@bruli.net>
To: o.pitzeier@uptime.at, ghoz@sympatico.ca, france@handhelds.org,
Jay.Estabrook@compaq.com, pollard@tomcat.admin.navo.hpc.mil
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5.26 - arch/alpha
Date: Fri, 9 Aug 2002 12:00:56 +0200 [thread overview]
Message-ID: <3D53AEF8.16231.E49799D@localhost> (raw)
In-Reply-To: <02072318292300.02533@shadowfax.middleearth>
On 23 Jul 2002, at 18:29, George France wrote:
> On Tuesday 23 July 2002 14:48, Oliver Pitzeier wrote:
> >
> > [ ... ]
> >
> > > You have made me aware that we have unintentionally created a
> > > private sort of club. I apologize. This will have to be corrected.
> >
> > That's not what I expected to read...
> > I think that this "private club" is not wrong at all... It just would
> > be nicer if there would be some kind of batch every week where all
> > alpha users/developers get a mail...
>
> I agree. We should send a weekly e-mail with the current status.
I did not see any news on the alpha/linux topic in lkml lately.
What is the way to keep in touch with the "private club" to help/
assist in getting further to a running 2.5.x kernel on alpha? I
am still on 2.4.18 on my test system.
Did anybody use gcc-3.0.x or gcc-3.1? With gcc-3.0.4 I
successfully built 2.4.18 but some applications don't run
correctly (eg. MySQL -> Parser). Is the kernel compilable
with gcc-3.1? Today I am using gcc-2.95.3 and I think is
ok; better than egcs (generates less unaligned traps at
runtime without changing the source).
Greetings,
Martin
next parent reply other threads:[~2002-08-09 9:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002b01c23279$84be70a0$1211a8c0@pitzeier.priv.at>
[not found] ` <02072318292300.02533@shadowfax.middleearth>
2002-08-09 10:00 ` Martin Brulisauer [this message]
2002-08-09 14:23 ` kbuild 2.5.26 - arch/alpha George France
2002-08-09 17:51 ` Måns Rullgård
2002-08-09 21:03 ` Thunder from the hill
[not found] <20020723202538.NYJJ13064.tomts23-srv.bellnexxia.net@there>
[not found] ` <001701c2329b$a812f6d0$1211a8c0@pitzeier.priv.at>
2002-07-23 23:26 ` Martin Brulisauer
[not found] <3D3DF93C.16904.30BF311@localhost>
[not found] ` <001a01c2329d$6d588fd0$1211a8c0@pitzeier.priv.at>
2002-07-23 23:21 ` Martin Brulisauer
2002-07-21 13:54 Martin Brulisauer
[not found] ` <001101c230d7$c5973c40$1211a8c0@pitzeier.priv.at>
2002-07-23 12:42 ` Martin Brulisauer
2002-07-23 13:28 ` Jan-Benedict Glaw
2002-07-23 23:34 ` Oliver Pitzeier
2002-07-24 6:53 ` Thunder from the hill
2002-07-24 7:07 ` Thunder from the hill
2002-07-24 7:13 ` Martin Brulisauer
2002-07-24 7:45 ` Thunder from the hill
2002-07-23 15:05 ` George France
2002-07-23 16:24 ` Ghozlane Toumi
2002-07-23 17:01 ` Martin Brulisauer
2002-07-23 19:00 ` George France
2002-07-23 19:08 ` Sven Koch
2002-07-23 21:24 ` Jay Estabrook
2002-07-23 20:18 ` Jay Estabrook
2002-07-23 23:44 ` Oliver Pitzeier
2002-07-23 23:35 ` Oliver Pitzeier
2002-07-23 23:54 ` Oliver Pitzeier
2002-07-24 3:51 ` Thunder from the hill
-- strict thread matches above, loose matches on Subject: below --
2002-07-20 8:41 Martin Brulisauer
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=3D53AEF8.16231.E49799D@localhost \
--to=martin@bruli.net \
--cc=Jay.Estabrook@compaq.com \
--cc=france@handhelds.org \
--cc=ghoz@sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=o.pitzeier@uptime.at \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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