From: hemarko <hemarko@fggm.osis.gov>
To: gcc-help@gcc.gnu.org
Cc: jubind@subexpgroup.com
Subject: Re: hppa2.ow-hp-hpux11.11
Date: Thu, 10 Jan 2002 08:58:00 -0000 [thread overview]
Message-ID: <3C3DD05A.B011B207@fggm.osis.gov> (raw)
This seems to be an artifact of the assembler putting in the assembly
date and time (which would of course differ between the stages. The
recommended fix (that I saw in the docs) was to just issue a plain make
which would pick up the last stage and make a final version.
I also received an e-mail that you can go to
http://dsportal.eservices.hp.com./dspp/tech_TechSoftwareDetailPage_IDX/1,1703,547,00.html
and get pointers to both the 32 and 64 bit versions of gcc-3.0.2 in both
source and binary.
--
Said the fox to the fish, "Join me ashore."
The fish are the Jews, Torah is our water.
Hillel (Sabba) Markowitz - sabbahem@bcpl.net
next reply other threads:[~2002-01-10 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 8:58 hemarko [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 22:21 hppa2.ow-hp-hpux11.11 Jubin
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=3C3DD05A.B011B207@fggm.osis.gov \
--to=hemarko@fggm.osis.gov \
--cc=gcc-help@gcc.gnu.org \
--cc=jubind@subexpgroup.com \
--cc=sabbahem@bcpl.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 read-only IMAP folder(s) and NNTP newsgroup(s).