linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shaw Terwilliger <sterwill@io.nu>
To: Hugh Caley <hcaley@loomer.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Paul's devel branch on Lombard?
Date: Thu, 9 Sep 1999 09:25:45 -0500	[thread overview]
Message-ID: <19990909092545.C4200@io.nu> (raw)
In-Reply-To: <37D74322.B787B9FE@loomer.com>


Hugh Caley wrote:
> I have not had this problem with building Paul's 2.2.12 kernel.  I did not use
> a config file from a previous version, which sounds like the major difference
> between us.

The problem is not with the 2.2.12 kernel, but with the 2.3.16 branch in
his "devel" archive.  The "stable" branch is working like a champ for me.
I'm sorry if I didn't make that very clear in my message (I had just
spent three minutes writing down all those addresses).  :)

> Or:  which version of gcc are you using?  I'm using the gcc from the fsirl
> directory on dev.linuxppc.org, and the glibc and related files from the same
> site.

If it matters, I'm using GCC from the Debian Potato branch (which I have
installed).  I believe it's just EGCS 1.1.2 release; but it's building 
2.2.12 great, 2.3.16 just isn't building.  I guess it's possible there's
a 2.3 kernel problem with the compiler, although I don't see any problems
in the builds.

Has anyone built kernels (either 2.2 or 2.3) with GCC 2.95?  I'd build a new
compiler (even just to try) if I could build the newest one.  :P


-- 
Shaw Terwilliger (sterwill@io.nu)

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-09-09 14:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-09  5:18 Paul's devel branch on Lombard? Hugh Caley
1999-09-09 14:25 ` Shaw Terwilliger [this message]
1999-09-09 14:51   ` Hugh Caley
1999-09-09 21:03     ` Martin Costabel
1999-09-09 21:30       ` Shaw Terwilliger
1999-09-09 22:45         ` Martin Costabel
1999-09-10  0:07           ` David D. Kilzer
1999-09-10  0:29             ` Paul Mackerras
1999-09-10  9:42             ` Geert Uytterhoeven
1999-09-10  9:46           ` Geert Uytterhoeven
1999-09-10 17:49             ` Martin Costabel
1999-09-10 22:08               ` 2.3.18 and CONFIG_ADB_MOUSE Martin Costabel
1999-09-10 23:55                 ` Joshua M. Thompson
1999-09-11  8:04                   ` Martin Costabel
1999-09-13  5:43                     ` Joshua M. Thompson
1999-09-13  6:55                       ` Martin Costabel
1999-09-13  7:29                         ` Geert Uytterhoeven
1999-09-13  8:32                           ` Martin Costabel
1999-09-13  8:54                             ` Geert Uytterhoeven
1999-09-11  3:37                 ` Paul Mackerras
1999-09-11  3:47                 ` David D. Kilzer
  -- strict thread matches above, loose matches on Subject: below --
1999-09-08 20:02 Paul's devel branch on Lombard? Shaw Terwilliger

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=19990909092545.C4200@io.nu \
    --to=sterwill@io.nu \
    --cc=hcaley@loomer.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).