Regarding gcc testsuite

Regarding gcc testsuite

[Manpreet Singh]

Hi,
     I want to run gcc testsuite(gcc-4.4.5) for newly build compiler
ppc_oea-gcc. But in my pc it is gcc-4.4.8. How would i run the gcc
testsuite-4.4.5 using compiler ppc_oea-gcc not the default one which
is gcc(4.8). How would i  set up dejagnu or any other way.

Thanks & regards
mappy

Re: Regarding gcc testsuite

[Jonathan Wakely]

On 27 October 2014 09:55, Manpreet Singh wrote:
> Hi,
>      I want to run gcc testsuite(gcc-4.4.5) for newly build compiler
> ppc_oea-gcc. But in my pc it is gcc-4.4.8. How would i run the gcc
> testsuite-4.4.5 using compiler ppc_oea-gcc not the default one which
> is gcc(4.8). How would i  set up dejagnu or any other way.

You run 'make check' after building gcc.

https://gcc.gnu.org/wiki/Testing_GCC

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
Failures from gcc testsuite after building gcc-4.4.5 and running make check
# of unexpected failures	5000
build_dir/.../gcc-4.4/gcc_test/gcc_test/gcc/xgcc  version 4.4.5 (GCC)

gcc log file shows this failure
Excess errors: build_dir/.../gcc-4.4/gcc_test/gcc/as: 76: exec: :
Permission denied

Thanks & regards
Manpreet Singh

On 10/27/14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 27 October 2014 09:55, Manpreet Singh wrote:
>> Hi,
>>      I want to run gcc testsuite(gcc-4.4.5) for newly build compiler
>> ppc_oea-gcc. But in my pc it is gcc-4.4.8. How would i run the gcc
>> testsuite-4.4.5 using compiler ppc_oea-gcc not the default one which
>> is gcc(4.8). How would i  set up dejagnu or any other way.
>
> You run 'make check' after building gcc.
>
> https://gcc.gnu.org/wiki/Testing_GCC
>

Re: Regarding gcc testsuite

[Jonathan Wakely]

On 27 October 2014 12:36, Manpreet Singh wrote:
> Hi,
> Failures from gcc testsuite after building gcc-4.4.5 and running make check
> # of unexpected failures        5000
> build_dir/.../gcc-4.4/gcc_test/gcc_test/gcc/xgcc  version 4.4.5 (GCC)
>
> gcc log file shows this failure
> Excess errors: build_dir/.../gcc-4.4/gcc_test/gcc/as: 76: exec: :
> Permission denied

Obvious question ... what is that file and what are its permissions?

If you don't have a valid assembler in your PATH the testsuite isn't
going to work very well.

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
     as is a shell-script with read and write permissions.
Also, when i am trying to build gcc-4.4.5, i am getting texi.info
errors, but when i used echo "MAKEINFO = :" >> Makefile in command
line, it get compiled without errors. Do i need to configure it again
or not. I am building for powerpc(target).

Thanks & regards
mappy

On 10/27/14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 27 October 2014 12:36, Manpreet Singh wrote:
>> Hi,
>> Failures from gcc testsuite after building gcc-4.4.5 and running make
>> check
>> # of unexpected failures        5000
>> build_dir/.../gcc-4.4/gcc_test/gcc_test/gcc/xgcc  version 4.4.5 (GCC)
>>
>> gcc log file shows this failure
>> Excess errors: build_dir/.../gcc-4.4/gcc_test/gcc/as: 76: exec: :
>> Permission denied
>
> Obvious question ... what is that file and what are its permissions?
>
> If you don't have a valid assembler in your PATH the testsuite isn't
> going to work very well.
>

Re: Regarding gcc testsuite

[Jonathan Wakely]

On 27 October 2014 15:46, Manpreet Singh wrote:
> Hi,
>      as is a shell-script with read and write permissions.

It should be executable.


> Also, when i am trying to build gcc-4.4.5, i am getting texi.info
> errors, but when i used echo "MAKEINFO = :" >> Makefile in command
> line, it get compiled without errors. Do i need to configure it again
> or not. I am building for powerpc(target).

That's an unrelated issue. You don't need to configure again.

Documentation in old versions of GCC is incompatible with modern
versions of Texinfo.  You can either add MAKEINFO=missing to the
configure command, or do something like your workaround.

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
    Thanks, now i can build it without error. But, when i run that
make check(testsuite) in command line.
Again giving lots of failure.
  e.g
/tmp/cc7EMVR7.s: Assembler messages:
/tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
/tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
/tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
same failure many thousand times.
How would i get rid off this failure?

Thanks & regards
mappy

On 10/27/14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 27 October 2014 15:46, Manpreet Singh wrote:
>> Hi,
>>      as is a shell-script with read and write permissions.
>
> It should be executable.
>
>
>> Also, when i am trying to build gcc-4.4.5, i am getting texi.info
>> errors, but when i used echo "MAKEINFO = :" >> Makefile in command
>> line, it get compiled without errors. Do i need to configure it again
>> or not. I am building for powerpc(target).
>
> That's an unrelated issue. You don't need to configure again.
>
> Documentation in old versions of GCC is incompatible with modern
> versions of Texinfo.  You can either add MAKEINFO=missing to the
> configure command, or do something like your workaround.
>

Re: Regarding gcc testsuite

[Jonathan Wakely]

On 28 October 2014 10:33, Manpreet Singh wrote:
> Hi,
>     Thanks, now i can build it without error. But, when i run that
> make check(testsuite) in command line.
> Again giving lots of failure.
>   e.g
> /tmp/cc7EMVR7.s: Assembler messages:
> /tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
> /tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
> /tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
> same failure many thousand times.
> How would i get rid off this failure?

Your assembler doesn't understand x86_64 instructions. I would guess
either you've got a 32-bit x86 assembler or an assembler for a totally
different architecture.

It would probably help if you said what kind of system you're running
on and how you configured GCC, so we don't have to guess what you're
trying to do.

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
    You are right its 32-bit assembler. I tried these 2 ways to configure

Way 1
My configuration:-
In my pc latest version of gcc-4.8 is install and i want to configure
and run gcc testsuite for gcc-4.4.5
Ubuntu 14.04
Host    =   x86_64-linux-gnu
Build   =   x86_64-linux-gnu
Target  =   powerpc-linux-gnu

These are the steps which i performed to run testsuite
 I am trying to run configure with this script

a)  sourcedir.../gcc-4.4.5/configure  --prefix=/tmp/gcc-4.4.5
--enable-languages=c,c++ --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=powerpc-linux-gnu
--enable-languages=c,c++ --enable-long-long


b)  And then to build gcc :-
make all-gcc

c)  To run the testsuite :-  builddir.../gcc-4.4.5/gcc
make check (in build dir)

This is the failure when i configured gcc-4.4.5 with above script
Failure is
FAIL: gcc.c-torture/compile/20000105-1.c  -O0  (test for excess errors)
Excess errors:
/build_dir.../gcc-4.4/new_build/gcc/as: 76: exec: : Permission denied
same failure many thousand times.

_________________________________________________________________________________________________________________________________________________________________________________________________________

Way 2

a)  I used already built assembler  i.e. i already mentioned above is
32 bit assembler
 sourcedir.../gcc-4.4.5/configure --prefix=/tmp/gcc-4.4.5
--with-as=/path/to/..../bin/ppc_oea-as
--with-ld=/path/to/..../bin/ppc_oea-ld --enable-languages=c,c++
--disable-bootstrap --disable-libgomp --disable-libstdcxx-pch
--with-ranlib=/path/to/..../bin/ppc_oea-ranlib


b)  And then to build gcc :-
make all-gcc

c)  To run the testsuite :-  builddir.../gcc-4.4.5/gcc
make check(in build dir)


And this the failure when i configured with way 2

/tmp/cc7EMVR7.s: Assembler messages:
/tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
/tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
/tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
same failure many thousand times.

Thanks & regards
Manpreet Singh

On 10/28/14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 28 October 2014 10:33, Manpreet Singh wrote:
>> Hi,
>>     Thanks, now i can build it without error. But, when i run that
>> make check(testsuite) in command line.
>> Again giving lots of failure.
>>   e.g
>> /tmp/cc7EMVR7.s: Assembler messages:
>> /tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
>> /tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
>> /tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
>> same failure many thousand times.
>> How would i get rid off this failure?
>
> Your assembler doesn't understand x86_64 instructions. I would guess
> either you've got a 32-bit x86 assembler or an assembler for a totally
> different architecture.
>
> It would probably help if you said what kind of system you're running
> on and how you configured GCC, so we don't have to guess what you're
> trying to do.
>

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
   According to my last mail. Is there any way to figure out the issue?

Thanks & regards
mappy

On 10/28/14, Manpreet Singh <mappysingh@gmail.com> wrote:
> Hi,
>     You are right its 32-bit assembler. I tried these 2 ways to configure
>
> Way 1
> My configuration:-
> In my pc latest version of gcc-4.8 is install and i want to configure
> and run gcc testsuite for gcc-4.4.5
> Ubuntu 14.04
> Host    =   x86_64-linux-gnu
> Build   =   x86_64-linux-gnu
> Target  =   powerpc-linux-gnu
>
> These are the steps which i performed to run testsuite
>  I am trying to run configure with this script
>
> a)  sourcedir.../gcc-4.4.5/configure  --prefix=/tmp/gcc-4.4.5
> --enable-languages=c,c++ --build=x86_64-pc-linux-gnu
> --host=x86_64-pc-linux-gnu --target=powerpc-linux-gnu
> --enable-languages=c,c++ --enable-long-long
>
>
> b)  And then to build gcc :-
> make all-gcc
>
> c)  To run the testsuite :-  builddir.../gcc-4.4.5/gcc
> make check (in build dir)
>
> This is the failure when i configured gcc-4.4.5 with above script
> Failure is
> FAIL: gcc.c-torture/compile/20000105-1.c  -O0  (test for excess errors)
> Excess errors:
> /build_dir.../gcc-4.4/new_build/gcc/as: 76: exec: : Permission denied
> same failure many thousand times.
>
> _________________________________________________________________________________________________________________________________________________________________________________________________________
>
> Way 2
>
> a)  I used already built assembler  i.e. i already mentioned above is
> 32 bit assembler
>  sourcedir.../gcc-4.4.5/configure --prefix=/tmp/gcc-4.4.5
> --with-as=/path/to/..../bin/ppc_oea-as
> --with-ld=/path/to/..../bin/ppc_oea-ld --enable-languages=c,c++
> --disable-bootstrap --disable-libgomp --disable-libstdcxx-pch
> --with-ranlib=/path/to/..../bin/ppc_oea-ranlib
>
>
> b)  And then to build gcc :-
> make all-gcc
>
> c)  To run the testsuite :-  builddir.../gcc-4.4.5/gcc
> make check(in build dir)
>
>
> And this the failure when i configured with way 2
>
> /tmp/cc7EMVR7.s: Assembler messages:
> /tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
> /tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
> /tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
> same failure many thousand times.
>
> Thanks & regards
> Manpreet Singh
>
> On 10/28/14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>> On 28 October 2014 10:33, Manpreet Singh wrote:
>>> Hi,
>>>     Thanks, now i can build it without error. But, when i run that
>>> make check(testsuite) in command line.
>>> Again giving lots of failure.
>>>   e.g
>>> /tmp/cc7EMVR7.s: Assembler messages:
>>> /tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
>>> /tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
>>> /tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
>>> same failure many thousand times.
>>> How would i get rid off this failure?
>>
>> Your assembler doesn't understand x86_64 instructions. I would guess
>> either you've got a 32-bit x86 assembler or an assembler for a totally
>> different architecture.
>>
>> It would probably help if you said what kind of system you're running
>> on and how you configured GCC, so we don't have to guess what you're
>> trying to do.
>>
>

Re: Regarding gcc testsuite

[Jonathan Wakely]

On 28 October 2014 12:06, Manpreet Singh wrote:
> Hi,
>     You are right its 32-bit assembler. I tried these 2 ways to configure
>
> Way 1
> My configuration:-
> In my pc latest version of gcc-4.8 is install and i want to configure
> and run gcc testsuite for gcc-4.4.5
> Ubuntu 14.04
> Host    =   x86_64-linux-gnu
> Build   =   x86_64-linux-gnu
> Target  =   powerpc-linux-gnu

You should have said you were building a cross-compiler.

You can't test a powerpc compiler on x86_64 directly. Your x86_64
machine can't run the powerpc executables.

The https://gcc.gnu.org/wiki/Testing_GCC#Testing_with_a_simulator link
I've already given explains how to use a simulator, but I don't know
if that's possible for powerpc. You might have to test the compiler on
a powerpc machine.

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
  I am trying to run the gcc-4.4.5 testsuite
with the credentials given below
Host    =   x86_64-linux-gnu
Build   =   x86_64-linux-gnu
Target  =   powerpc-linux-gnu
and with this script

sudo runtest RUNTESTFLAGS="CFLAGS_FOR_TARGET=--sysroot=/opt/.../cdk/ppc/oea
 --target_board=powerpc-sim" --tool gcc --srcdir
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite
--tool_exec=/opt/.../cdk/ppc/oea/bin/ppc_oea-gcc

target libraries directory = /opt/.../cdk/ppc/oea

I also have sparc_v8-gcc and x86_i586-gcc executable

i got these errors

/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-torture/execute/builtins/fprintf.c:8:19:
error: stdio.h: No such file or directory
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-torture/execute/builtins/fprintf.c:9:
error: expected ')' before '*' token
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-torture/execute/builtins/fprintf.c:
In function 'main_test':
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-torture/execute/builtins/fprintf.c:15:
error: 'FILE' undeclared (first use in this function)
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-torture/execute/builtins/fprintf.c:15:
error: (Each undeclared identifier is reported only once
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-torture/execute/builtins/fprintf.c:15:
error: for each function it appears in.)
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-torture/execute/builtins/fprintf.c:15:
error: 's_array' undeclared (first use in this function)

Thanks & regards
mappy

On 10/29/14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 28 October 2014 12:06, Manpreet Singh wrote:
>> Hi,
>>     You are right its 32-bit assembler. I tried these 2 ways to configure
>>
>> Way 1
>> My configuration:-
>> In my pc latest version of gcc-4.8 is install and i want to configure
>> and run gcc testsuite for gcc-4.4.5
>> Ubuntu 14.04
>> Host    =   x86_64-linux-gnu
>> Build   =   x86_64-linux-gnu
>> Target  =   powerpc-linux-gnu
>
> You should have said you were building a cross-compiler.
>
> You can't test a powerpc compiler on x86_64 directly. Your x86_64
> machine can't run the powerpc executables.
>
> The https://gcc.gnu.org/wiki/Testing_GCC#Testing_with_a_simulator link
> I've already given explains how to use a simulator, but I don't know
> if that's possible for powerpc. You might have to test the compiler on
> a powerpc machine.
>

RE: Regarding gcc testsuite

[Andrew Bennett]

> Hi,
>   I am trying to run the gcc-4.4.5 testsuite
> with the credentials given below
> Host    =   x86_64-linux-gnu
> Build   =   x86_64-linux-gnu
> Target  =   powerpc-linux-gnu
> and with this script
> 
> sudo runtest RUNTESTFLAGS="CFLAGS_FOR_TARGET=--sysroot=/opt/.../cdk/ppc/oea
>  --target_board=powerpc-sim" --tool gcc --srcdir
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite
> --tool_exec=/opt/.../cdk/ppc/oea/bin/ppc_oea-gcc
> 
> target libraries directory = /opt/.../cdk/ppc/oea
> 
> I also have sparc_v8-gcc and x86_i586-gcc executable
> 
> i got these errors
> 
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
> torture/execute/builtins/fprintf.c:8:19:
> error: stdio.h: No such file or directory
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
> torture/execute/builtins/fprintf.c:9:
> error: expected ')' before '*' token
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
> torture/execute/builtins/fprintf.c:
> In function 'main_test':
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
> torture/execute/builtins/fprintf.c:15:
> error: 'FILE' undeclared (first use in this function)
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
> torture/execute/builtins/fprintf.c:15:
> error: (Each undeclared identifier is reported only once
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
> torture/execute/builtins/fprintf.c:15:
> error: for each function it appears in.)
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
> torture/execute/builtins/fprintf.c:15:
> error: 's_array' undeclared (first use in this function)

This is the same issue that I commented on in:

https://gcc.gnu.org/ml/gcc/2014-10/msg00164.html


Could you check that you have correctly built and installed newlib?


Regards,


Andrew

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
    Now, i am just trying to run gcc-4.4.5 testsuite with already
built compilers. I have complete package, which has these compilers,
ppc_oea-gcc, sparc_v8-gcc, x86_i586-gcc. I am just trying to run
gcc-4.4.5 testsuite by tweaking one of these compilers.
This package is correctly built. How would i find newlib ? I tried,
but i couldn't find it.

Thanks & regards
Manpreet Singh

On 10/30/14, Andrew Bennett <Andrew.Bennett@imgtec.com> wrote:
>> Hi,
>>   I am trying to run the gcc-4.4.5 testsuite
>> with the credentials given below
>> Host    =   x86_64-linux-gnu
>> Build   =   x86_64-linux-gnu
>> Target  =   powerpc-linux-gnu
>> and with this script
>>
>> sudo runtest
>> RUNTESTFLAGS="CFLAGS_FOR_TARGET=--sysroot=/opt/.../cdk/ppc/oea
>>  --target_board=powerpc-sim" --tool gcc --srcdir
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite
>> --tool_exec=/opt/.../cdk/ppc/oea/bin/ppc_oea-gcc
>>
>> target libraries directory = /opt/.../cdk/ppc/oea
>>
>> I also have sparc_v8-gcc and x86_i586-gcc executable
>>
>> i got these errors
>>
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:8:19:
>> error: stdio.h: No such file or directory
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:9:
>> error: expected ')' before '*' token
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:
>> In function 'main_test':
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: 'FILE' undeclared (first use in this function)
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: (Each undeclared identifier is reported only once
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: for each function it appears in.)
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: 's_array' undeclared (first use in this function)
>
> This is the same issue that I commented on in:
>
> https://gcc.gnu.org/ml/gcc/2014-10/msg00164.html
>
>
> Could you check that you have correctly built and installed newlib?
>
>
> Regards,
>
>
> Andrew
>

Re: Regarding gcc testsuite

[Manpreet Singh]

Hi,
   I am trying to run this gcc-4.4.5 testsuite with this script
 sudo runtest --target_board=sparc-sim  --tool gcc --srcdir
/home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite
--tool_exec=/opt/..cdk/sparc/v8/bin/sparc_v8-gcc

These are the failures after running this script
 /sparc-unknown-elf/bin/ld: cannot open linker script file elfsim.ld:
No such file or directory

If this error related to linker then how would i set linker or pass
options to runtest.

Thanks & regards
mappy



On 10/30/14, Andrew Bennett <Andrew.Bennett@imgtec.com> wrote:
>> Hi,
>>   I am trying to run the gcc-4.4.5 testsuite
>> with the credentials given below
>> Host    =   x86_64-linux-gnu
>> Build   =   x86_64-linux-gnu
>> Target  =   powerpc-linux-gnu
>> and with this script
>>
>> sudo runtest
>> RUNTESTFLAGS="CFLAGS_FOR_TARGET=--sysroot=/opt/.../cdk/ppc/oea
>>  --target_board=powerpc-sim" --tool gcc --srcdir
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite
>> --tool_exec=/opt/.../cdk/ppc/oea/bin/ppc_oea-gcc
>>
>> target libraries directory = /opt/.../cdk/ppc/oea
>>
>> I also have sparc_v8-gcc and x86_i586-gcc executable
>>
>> i got these errors
>>
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:8:19:
>> error: stdio.h: No such file or directory
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:9:
>> error: expected ')' before '*' token
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:
>> In function 'main_test':
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: 'FILE' undeclared (first use in this function)
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: (Each undeclared identifier is reported only once
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: for each function it appears in.)
>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>> torture/execute/builtins/fprintf.c:15:
>> error: 's_array' undeclared (first use in this function)
>
> This is the same issue that I commented on in:
>
> https://gcc.gnu.org/ml/gcc/2014-10/msg00164.html
>
>
> Could you check that you have correctly built and installed newlib?
>
>
> Regards,
>
>
> Andrew
>

Re: Regarding gcc testsuite

[Cherry Vanc]

Please see if this previous message helps your case
https://www.sourceware.org/ml/crossgcc/2006-04/msg00159.html

On Fri, Oct 31, 2014 at 3:31 AM, Manpreet Singh <mappysingh@gmail.com> wrote:
> Hi,
>    I am trying to run this gcc-4.4.5 testsuite with this script
>  sudo runtest --target_board=sparc-sim  --tool gcc --srcdir
> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite
> --tool_exec=/opt/..cdk/sparc/v8/bin/sparc_v8-gcc
>
> These are the failures after running this script
>  /sparc-unknown-elf/bin/ld: cannot open linker script file elfsim.ld:
> No such file or directory
>
> If this error related to linker then how would i set linker or pass
> options to runtest.
>
> Thanks & regards
> mappy
>
>
>
> On 10/30/14, Andrew Bennett <Andrew.Bennett@imgtec.com> wrote:
>>> Hi,
>>>   I am trying to run the gcc-4.4.5 testsuite
>>> with the credentials given below
>>> Host    =   x86_64-linux-gnu
>>> Build   =   x86_64-linux-gnu
>>> Target  =   powerpc-linux-gnu
>>> and with this script
>>>
>>> sudo runtest
>>> RUNTESTFLAGS="CFLAGS_FOR_TARGET=--sysroot=/opt/.../cdk/ppc/oea
>>>  --target_board=powerpc-sim" --tool gcc --srcdir
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite
>>> --tool_exec=/opt/.../cdk/ppc/oea/bin/ppc_oea-gcc
>>>
>>> target libraries directory = /opt/.../cdk/ppc/oea
>>>
>>> I also have sparc_v8-gcc and x86_i586-gcc executable
>>>
>>> i got these errors
>>>
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>>> torture/execute/builtins/fprintf.c:8:19:
>>> error: stdio.h: No such file or directory
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>>> torture/execute/builtins/fprintf.c:9:
>>> error: expected ')' before '*' token
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>>> torture/execute/builtins/fprintf.c:
>>> In function 'main_test':
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>>> torture/execute/builtins/fprintf.c:15:
>>> error: 'FILE' undeclared (first use in this function)
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>>> torture/execute/builtins/fprintf.c:15:
>>> error: (Each undeclared identifier is reported only once
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>>> torture/execute/builtins/fprintf.c:15:
>>> error: for each function it appears in.)
>>> /home/gcc-test/gcc4.5/gcc-4.4.5/gcc/testsuite/gcc.c-
>>> torture/execute/builtins/fprintf.c:15:
>>> error: 's_array' undeclared (first use in this function)
>>
>> This is the same issue that I commented on in:
>>
>> https://gcc.gnu.org/ml/gcc/2014-10/msg00164.html
>>
>>
>> Could you check that you have correctly built and installed newlib?
>>
>>
>> Regards,
>>
>>
>> Andrew
>>

Regarding gcc testsuite

[Manpreet Singh]

Hi,
    I am trying to run gcc-4.4.5 testsuite , but everytime i run it, i
got lots of failure
e.g unexpected failures	13000

My configuration:-
In my pc latest version of gcc-4.8 is install and i want to configure
and run gcc testsuite for gcc-4.4.5
Ubuntu 14.04
Host    =   x86_64-linux-gnu
Build   =   x86_64-linux-gnu
Target  =   powerpc-linux-gnu

These are the steps which i performed to run testsuite
1. I am trying to run configure with this script

sourcedir.../gcc-4.4.5/configure  --prefix=/tmp/gcc-4.4.5
--enable-languages=c,c++ --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=powerpc-linux-gnu
--enable-languages=c,c++ --enable-long-long


2. And then to build gcc :-
make all-gcc

3. To run the testsuite :-  sourcedir.../gcc-4.4.5/gcc
make check

It generates lot of failures

Dejagnu :- latest version

Thanks & regards
Mappy