public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Smilodon <smilodon@niksula.hut.fi>
To: egcs@egcs.cygnus.com
Subject: EGCS 1.1.2 (egcs-2.91.66) compiled
Date: Sun, 21 Mar 1999 13:37:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.95.990321233039.30165A-100000@jt7-234.tky.hut.fi> (raw)

config.guess: 
i586-pc-linux-gnu

Compiled successfully, after some twiddling: At first tries, the compile
bombed with xgcc giving an error message akin to 'cannot execute -m'.
After running the config.status script in _objdir_ it worked all right,
as it replaced relative paths with absolute ones or something. My guess is
that it skipped building cc1plus for some reason.

	--Smilodon.

WARNING: multiple messages have this Message-ID
From: Smilodon <smilodon@niksula.hut.fi>
To: egcs@egcs.cygnus.com
Subject: EGCS 1.1.2 (egcs-2.91.66) compiled
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.95.990321233039.30165A-100000@jt7-234.tky.hut.fi> (raw)
Message-ID: <19990331234600.mx1AehOhbIg9Ntljv7wxmkcLUFoaG_dPwP-fuUjWp2w@z> (raw)

config.guess: 
i586-pc-linux-gnu

Compiled successfully, after some twiddling: At first tries, the compile
bombed with xgcc giving an error message akin to 'cannot execute -m'.
After running the config.status script in _objdir_ it worked all right,
as it replaced relative paths with absolute ones or something. My guess is
that it skipped building cc1plus for some reason.

	--Smilodon.


             reply	other threads:[~1999-03-21 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-21 13:37 Smilodon [this message]
1999-03-31 23:46 ` Smilodon

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.3.95.990321233039.30165A-100000@jt7-234.tky.hut.fi \
    --to=smilodon@niksula.hut.fi \
    --cc=egcs@egcs.cygnus.com \
    /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).