From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] compiling kernels with gcc-3.2
Date: Sat, 13 Jul 2002 14:54:19 -0400 [thread overview]
Message-ID: <20020713185419.GA9983@systemhalted> (raw)
In-Reply-To: <20020713052016.GA10191@tausq.org>
>
> tausq@a500:~$ uname -a
> Linux version 2.4.18-pa54 (tausq@a500) (gcc version 3.2 20020711 (experimental)) #2 SMP Fri Jul 12 22:04:23 PDT 2002
> tausq@a500:~$
>
> I'm quite perplexed about why it doesn't seem to always work for
> others... i didn't really have to do anything special with either gcc or
> the kernel to get it to boot.
>
> randolph
I think the issue is one of quality assurance. We don't have a strict
set of criteria for testing/validating/certifying that a given snapshot
of a given toolchain, in a given configuration, will work.
I'm trying to address some of these things by building a cross-check
test-suite to test the toolchain weekly or nightly. This all came out
of a talk I had with Matt Taggart :) who is another toolchain-junkie.
When I get more work done I'll post.
c.
next prev parent reply other threads:[~2002-07-13 18:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 7:36 [parisc-linux] compiling kernels with gcc-3.1 Randolph Chung
2002-07-12 9:49 ` joel.soete
2002-07-12 15:01 ` Randolph Chung
2002-07-12 16:23 ` joel.soete
2002-07-15 7:03 ` joel.soete
2002-07-15 7:24 ` joel.soete
2002-07-15 15:06 ` Randolph Chung
2002-07-15 15:56 ` joel.soete
2002-07-15 15:24 ` John David Anglin
2002-07-15 15:52 ` joel.soete
2002-07-15 16:22 ` Randolph Chung
2002-07-15 17:13 ` John David Anglin
2002-07-15 17:27 ` joel.soete
2002-07-13 5:20 ` [parisc-linux] compiling kernels with gcc-3.2 Randolph Chung
2002-07-13 10:24 ` Joel Soete
2002-07-13 18:54 ` Carlos O'Donell [this message]
2002-07-13 17:06 ` [parisc-linux] compiling kernels with gcc-3.1 Joel Soete
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=20020713185419.GA9983@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@parisc-linux.org \
--cc=randolph@tausq.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