From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d30fbbf6343a12e1
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Gnat-3.04 source; builtin_setjmp/builtin_longjmp
Date: 1996/06/08
Message-ID: <dewar.834206621@schonberg>#1/1
X-Deja-AN: 159149264
references: <1996Jun6.142139.25487@relay.nswc.navy.mil>
 <u2d93bak3f.fsf@hola.gsyc.inf.uc3m.es>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-06-08T00:00:00+00:00
List-Id: <comp.lang.ada>


David Mann wrote

   "Has anyone found that they cannot built GNAT-3.04 from source because
   the target platform does not support the routines 'builtin_setjmp'
   and 'builtin_lonjmp'.  If so, are they any ideas on what some
   replacement routines (in C I presume) would look like?"

You need to do the build as follows, no shortcuts will work:

1. Build a new version of the C compiler
2. Build a new version of libgcc
3. Build GNAT making *sure* that you use the new C compiler and libgcc
You won't have any trouble if you do that. Most remaining problems come
from people not really following step 3 (they accidentally use an old C
compiler or an old libgcc).

Symptoms of failing to follow the proper procedure include:

  1. Complaints about missing externals for builtin setjmp, longjmp
       (this means that you are not using the new C compiler)


  2. Complaints about missing external for __dummy
       (this means that you are not using the new libgcc)

  3. Blowup during compiling the library (typically at a-ncelfu)
       (this means you have built GNAT inconsistently, partly using
        the new stuff and partly the old).