From: "Joël Soete" <jso@europay.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: carlos@baldric.uwo.ca, jso@europay.com,
jso <jso@europay.com> (Joël Soete),
parisc-linux@lists.parisc-linux.org, jso@hiauly1.hia.nrc.ca
Subject: Re: [parisc-linux] Re: hppa-linux gcc-3.0.3:
Date: Tue, 19 Feb 2002 18:03:22 +0100 [thread overview]
Message-ID: <OFDF1A47D3.4AEE03AD-ONC1256B65.005CFBD9@com> (raw)
David,
It seems Ok: just finished the first step of compiling gcc (snapshot dated
020218 from sources.redhat.com because I do not find where Matthias
uploaded its snapshot :( ) with echo $? -> after make :-).
I will continue with glibc.
Thanks for all,
Joel
PS: with gcc snapshot, I also find gcc-core-xxx.bz2. Do know what is it?
(Do I need it?)
=
=20
"John David =
=20
Anglin" To: jso@europay.com (Jo=EBl =
Soete) =20
<dave@hiauly1.h cc: carlos@baldric.uwo.ca, j=
so@europay.com, "jso"@hiauly1.hia.nrc.ca,=20
ia.nrc.ca> <jso@europay.com>, parisc-linux@=
lists.parisc-linux.org, "jso" =20
@hiauly1.hia.nrc.ca =
=20
19-02-02 04:58 Subject: Re: [parisc-linux] =
Re: hppa-linux gcc-3.0.3: =20
PM =
=20
=
=20
=
=20
> Just finished to compile binutils. All seems Ok.
> I just notice many "WARNING: could not find 'runtest'" when "make -k
> check". Is it normal?
This is normal:
if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
$runtest --tool libstdc++-v3 --srcdir $srcdir ; \
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
fi
WARNING: Couldn't find the global config file.
WARNING: Couldn't find tool init file
You can get rid of the "global config" warning by installing a global
config file for dejagnu. There is as sample in the distribution.
If you actually see your warning and not just the Makefile command,
then you have a problem with your dejagnu installation or PATH variable.
In order to run the testsuite, you need dejagnu, expect and tcl
installed. They may require some other packages as well for full
functionality.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX:
952-6605)
**********************************************************************
This e-mail and any attachments to it may contain confidential information =
which is strictly intended for the use of the authorised recipient. If you=
have received this e-mail in error, please delete it and notify the sender=
by replying to this e-mail.
Thank you for your co-operation.
**********************************************************************
next reply other threads:[~2002-02-19 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 17:03 Joël Soete [this message]
2002-02-19 21:57 ` [parisc-linux] Re: hppa-linux gcc-3.0.3: Matthias Klose
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 6:36 Joël Soete
2002-02-19 15:49 Joël Soete
2002-02-19 14:43 Joël Soete
2002-02-19 15:58 ` John David Anglin
2002-02-18 17:53 Joël Soete
2002-02-18 18:03 ` John David Anglin
2002-02-18 14:54 Joël Soete
2002-02-18 16:41 ` John David Anglin
2002-02-18 21:47 ` Matthias Klose
2002-02-18 21:54 ` John David Anglin
2002-02-18 10:19 Joël Soete
2002-02-18 14:29 ` Carlos O'Donell Jr.
2002-02-18 16:25 ` John David Anglin
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=OFDF1A47D3.4AEE03AD-ONC1256B65.005CFBD9@com \
--to=jso@europay.com \
--cc=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=jso@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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