From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Gnat-3.04 source; builtin_setjmp/builtin_longjmp
Date: 1996/06/08
Date: 1996-06-08T00:00:00+00:00 [thread overview]
Message-ID: <dewar.834206621@schonberg> (raw)
In-Reply-To: u2d93bak3f.fsf@hola.gsyc.inf.uc3m.es
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).
next prev parent reply other threads:[~1996-06-08 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-06 0:00 Gnat-3.04 source; builtin_setjmp/builtin_longjmp David Mann
1996-06-07 0:00 ` Jesus M. Gonzalez
1996-06-08 0:00 ` Robert Dewar [this message]
1996-06-08 0:00 ` Robert Dewar
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox