linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: Tom Rini <tmrini@ntplx.net>
Cc: Konstantinos Margaritis <kmargar@cc.uoa.gr>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: cvs kernel does not compile
Date: Wed, 12 May 1999 23:31:25 +0200	[thread overview]
Message-ID: <3739F32D.E4A5BD10@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.05.9905121539420.651-100000@pc.wackyland.com


Tom Rini wrote:
> 
> On Wed, 12 May 1999, Konstantinos Margaritis wrote:
> 
> >    The 2.3.0 kernel found on cvs.on.openprojects.net does not compile on
> > my powerpc system (debian glibc 2.1, egcs 1.1.2pre), with the following
> > error:
> 
> Welcome to the dev cycle.  The tree can be broken once again, and only has
> to compile on x86.  I'm sure Cort or someone will see what's going to be
> needed to fix up 2.3.1-pre2 soon enough.

2.3.0 (cvs) compiled fine for me this morning, I'm running it now
(LinuxPPC R5 beta):

root[8]#dmesg | grep Linux
Linux version 2.3.0 (root@chezmoi) (gcc version egcs-2.91.66 19990314
(egcs-1.1.2 release)) #14 Wed May 12 09:30:40 CEST 1999

--
Martin

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-05-12 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-12 14:08 cvs kernel does not compile Konstantinos Margaritis
1999-05-12 19:40 ` Tom Rini
1999-05-12 21:31   ` Martin Costabel [this message]
1999-05-12 21:37     ` Tom Rini
1999-05-13 11:57       ` Martin Costabel
1999-05-13 19:06       ` Sriranga Veeraraghavan
1999-05-13 21:59         ` Martin Costabel
1999-05-13 22:12         ` Tom Rini

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=3739F32D.E4A5BD10@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=kmargar@cc.uoa.gr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tmrini@ntplx.net \
    /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).