public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hannes Niemi <hniemi@csc.fi>
To: gcc-help@gcc.gnu.org
Cc: Hannes Niemi <hniemi@csc.fi>
Subject: Tru64 version 5.0 (fwd)
Date: Fri, 03 Mar 2000 02:18:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10003031218030.7670-100000@sampo.csc.fi> (raw)

Hi!

Have anyone ported gcc-2.95.x on Tru64 version 5.0
I managed to set up the configration by telling that host is 4.0.
However the building phase fails with cpp while building gcc. E.g. java is
bould up ok and some tools too.

When I try the cpp it fails and dumps core.

I am just wondering, before I start the real work, if someone has all
ready solved this.
	
	Hannes Niemi
	Hannes.Niemi@csc.fi
	puh: 	09 457 2098
	Osoite: Tekniikantie 15a D, PL 405,
                02101 ESPOO 


WARNING: multiple messages have this Message-ID
From: Hannes Niemi <hniemi@csc.fi>
To: gcc-help@gcc.gnu.org
Cc: Hannes Niemi <hniemi@csc.fi>
Subject: Tru64 version 5.0 (fwd)
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10003031218030.7670-100000@sampo.csc.fi> (raw)
Message-ID: <20000401000000.IbcZ7z6tWUwJ1qhYrp7UHozDyuGcyKGVR-hA7CfXKv4@z> (raw)

Hi!

Have anyone ported gcc-2.95.x on Tru64 version 5.0
I managed to set up the configration by telling that host is 4.0.
However the building phase fails with cpp while building gcc. E.g. java is
bould up ok and some tools too.

When I try the cpp it fails and dumps core.

I am just wondering, before I start the real work, if someone has all
ready solved this.
	
	Hannes Niemi
	Hannes.Niemi@csc.fi
	puh: 	09 457 2098
	Osoite: Tekniikantie 15a D, PL 405,
                02101 ESPOO 


             reply	other threads:[~2000-03-03  2:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-03  2:18 Hannes Niemi [this message]
2000-04-01  0:00 ` Hannes Niemi

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.10.10003031218030.7670-100000@sampo.csc.fi \
    --to=hniemi@csc.fi \
    --cc=gcc-help@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).