Richard Guenther wrote:
> On Tue, 13 Dec 2005, Arnaud Charlet wrote:
> > Except that unlike C, Ada needs a run-time, even for simple things,
> > so you need in addition to point (using e.g. -I) to the runtime,
> > which is built under obj/gcc/ada/rts,
> >
> > so from obj/gcc directory, you can do
The magic is only there to support testing in the build tree,
with the compiler not installed.
Assuming you've done a make install, then compiling an ACATS
test is as simple as:
Yeah, but the problem is that most of us don't want to do a "make install"
of a compiler that we know d
Can someone of the Ada folks provide some info how I can get a debugging
session with a failing acats test? Looking at the testsuite log file
I f.i. see c32001e failing and an (appearant) build line(s)
BUILD c32001e.adb
but neither of them is invokable from no existing direct
> /space/rguenther/obj/obj3/gcc/xgcc -c -B/space/rguenther/obj/obj3/gcc/
> -gnatws -O2 -I/space/rguenther/obj/obj3/gcc/testsuite/ada/acats/support
> /space/rguenther/obj/obj3/gcc/testsuite/ada/acats/tests/c3/c32001e/c32001e.adb
>
> -I/space/rguenther/obj/obj3/gcc/ada/rts
>
> ? This way it wou
On Tue, 13 Dec 2005, Arnaud Charlet wrote:
> > This is exactly what I'm trying to do, as I'm testing with the
> > stage1 compiler that happens to miscompile the stage2 compiler,
> > so I guessed it might be easier to debug the testsuite fallout
> > of the stage1 compiler.
> >
> > I'm used to do .
> This is exactly what I'm trying to do, as I'm testing with the
> stage1 compiler that happens to miscompile the stage2 compiler,
> so I guessed it might be easier to debug the testsuite fallout
> of the stage1 compiler.
>
> I'm used to do ./xgcc -B/whatever in the gcc/ directory, maybe
> gnatmak
On Tue, 13 Dec 2005, Arnaud Charlet wrote:
> > I see there's magic going on in the testsuite/ada/acats/run_acats and
> > run_all.sh scripts, but they cannot be invoked directly to set up the
> > environment.
>
> The magic is only there to support testing in the build tree,
> with the compiler not
> I see there's magic going on in the testsuite/ada/acats/run_acats and
> run_all.sh scripts, but they cannot be invoked directly to set up the
> environment.
The magic is only there to support testing in the build tree,
with the compiler not installed.
Assuming you've done a make install, then c
