public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ged Haywood <ged@www2.jubileegroup.co.uk>
To: gcc@gcc.gnu.org
Subject: Successful build of gcc 3.2.3 on Slackware 9.0
Date: Sun, 03 Aug 2003 16:37:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0308031715280.22381-101000@www2.jubileegroup.co.uk> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2433 bytes --]

Hello there,

The script below should tell you what you need to know.  For more info
check the attached file.  Sorry it's so big.  This is Slackware V9.0,
a fresh installation, on an AMD K6-II/400.  The only thing I had to do
before compiling gcc was install dejagnu 1.4.3.  Just in case it isn't
obvious, this was a full set of languages.  "make -k check" failed
after the objective-c tests; I'm not sure why yet, it may be that it's
expected.  I'm pretty sure I did it by the book.  It seems there are
no ada nor java tests that run stand-alone, is that right?

Currently I have troubles compiling, or at least with the tests, on
another PC (Intel PII/400) with a Slackware 9 that was upgraded from
Slackware 7.1, kernel 2.2.16.  That's the reason I installed on this
AMD PC.  I'll let you know when I fix the other system.  Don't hold
your breath.  I suspect a binary or library didn't get deleted.

Do please ask if you want any more details.

73,
Ged.
======================================================================
Script started on Sun Aug  3 07:24:56 2003
ged@tech:~/src/gcc-3.2.3$ 
ged@tech:~/src/gcc-3.2.3$ 
ged@tech:~/src/gcc-3.2.3$ ./config.guess
i586-pc-linux-gnu
ged@tech:~/src/gcc-3.2.3$ gcc -v
Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-gnu/3.2.3/specs
Configured with: ../gcc-3.2.3/configure 
Thread model: posix
gcc version 3.2.3
ged@tech:~/src/gcc-3.2.3$ 
ged@tech:~/src/gcc-3.2.3$ 
ged@tech:~/src/gcc-3.2.3$ uname -a
Linux tech 2.4.20 #2 Mon Mar 17 22:02:15 PST 2003 i586 unknown
ged@tech:~/src/gcc-3.2.3$ 
ged@tech:~/src/gcc-3.2.3$ 
ged@tech:~/src/gcc-3.2.3$ /lib/libc.so.6
GNU C Library stable release version 2.3.1, by Roland McGrath et al.
Copyright (C) 1992-2001, 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.2.2.
Compiled on a Linux 2.4.20 system on 2003-03-04.
Available extensions:
	GNU libio by Per Bothner
	crypt add-on version 2.1 by Michael Glad and others
	linuxthreads-0.10 by Xavier Leroy
	BIND-8.2.3-T5B
	libthread_db work sponsored by Alpha Processor Inc
	NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Report bugs using the `glibcbug' script to <bugs@gnu.org>.
ged@tech:~/src/gcc-3.2.3$ exit

Script done on Sun Aug  3 07:29:25 2003
======================================================================

[-- Attachment #2: Test summaries. --]
[-- Type: APPLICATION/x-gzip, Size: 122880 bytes --]

                 reply	other threads:[~2003-08-03 16:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.21.0308031715280.22381-101000@www2.jubileegroup.co.uk \
    --to=ged@www2.jubileegroup.co.uk \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).