public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cyrille Chepelov <chepelov@rip.ens-cachan.fr>
To: egcs@cygnus.com
Subject: egcs on Sparc/Linux  : 1.0.2 SUCCESS  980321 FAILURE
Date: Mon, 30 Mar 1998 16:18:00 -0000	[thread overview]
Message-ID: <Pine.GSO.3.96.980329234014.7898A-200000@aria> (raw)

Hi folks,

first of all, nice job ! At least a compiler one can compile nearly as if
it was gawk or GNU make...

Platform : 
----------

software : Linux kernel 2.0.30 (vanilla RedHat 4.2) with libc 5.3.12 
hardware : Sun SPARCstation IPX 
bootstrap compiler : gcc-2.7.2.1 (RH 4.2 binary)

config.guess says : sparc-unknown-linux-gnulibc1

-----

egcs-980321 : FAILURE
gas chokes when asked to build _muldi3 (libgcc2.c),
see egcs-make-boostrap-tail (tail -3 nohup.out)  [apologies in advance if
this is a FAQ]

egcs-1.0.2 : SUCCESS (nearly out of the box)
I had to define NEED_ATEXIT, otherwise gbl-ctors.h
was fighting with stdlib's definition of atexit().


Keep up the good job !

	-- Cyrille

                 reply	other threads:[~1998-03-30 16:18 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.GSO.3.96.980329234014.7898A-200000@aria \
    --to=chepelov@rip.ens-cachan.fr \
    --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).