public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manush Dodunekov <manush@litecom.se>
To: egcs@cygnus.com
Subject: egcs-1.0 build success on i586-pc-linux-gnu
Date: Sat, 06 Dec 1997 19:23:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.971207041328.14882A-100000@matrix.litecom.se> (raw)

Previously i had some random SIGSEGVs in code that used libstdc++2.7.2.8
and pthreads (the linuxthreads with glibc2.0.5c), compiled with
gcc2.7.2.3. Now everything is recompiled with egcs-1.0, and works just
great!

--------------------------------------------
Manush Dodunekov / LiteCom Interactive Media
  manush@litecom.se, http://www.litecom.se
--------------------------------------------


                 reply	other threads:[~1997-12-06 19:23 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.3.96.971207041328.14882A-100000@matrix.litecom.se \
    --to=manush@litecom.se \
    --cc=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).