Help needed to buid GCC for NEC V850

Help needed to buid GCC for NEC V850

[gowrisankar loganathan]

Hello All,
        I am trying to build GCC cross compiler for V850, I am using the following files
 
gcc-4.3.3
 
binutils-2.19.1
 
for configuration I used the following options
 
$  ../Gcc_Source/gcc-4.3.3/configure --target=v850-elf --host=i686-pc-cygwin -enable-language=c --prefix=c:/gcc/v850 --with-gnu-as --with-gnuld  --disable-win32-registry
 
after the config I used 
 
$ make
 
now I got the error as 
 
gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../Gcc_Source/gcc-4.3.3/libiberty/../incl
ude  -W -Wall -Wwrite-strings -Wstrict-prototypes -pedantic  ../../Gcc_Source/gc
c-4.3.3/libiberty/pex-unix.c -o pex-unix.o
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_wait':
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:223: warning: implicit declarati
on of function `wait'
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: At top level:
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:356: warning: function declarati
on isn't a prototype
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_unix_exec_chil
d':
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:375: warning: implicit declarati
on of function `fork'
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:378: warning: implicit declarati
on of function `sleep'
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:428: warning: passing arg 2 of `
execvp' from incompatible pointer type
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:433: warning: passing arg 2 of `
execv' from incompatible pointer type
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_unix_wait':
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:484: warning: implicit declarati
on of function `kill'
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_unix_pipe':
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:502: warning: implicit declarati
on of function `pipe'
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_unix_fdopenw':
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: warning: implicit declarati
on of function `fcntl'
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `F_SETFD' undeclared
 (first use in this function)
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: (Each undeclared ide
ntifier is reported only once
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: for each function it
 appears in.)
../../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `FD_CLOEXEC' undecla
red (first use in this function)
make[2]: *** [pex-unix.o] Error 1
make[2]: Leaving directory `/cygdrive/c/temp/gcc_Installation/libiberty'
make[1]: *** [all-libiberty] Error 2
make[1]: Leaving directory `/cygdrive/c/temp/gcc_Installation'
make: *** [all] Error 2
 
 
Can any one help me to fix the issue.
 
 
With Thanks & Regards,
Gowrisankar Loganathan
_________________________________________________________________
Windows Live Messenger. Multitasking at its finest.
http://www.microsoft.com/india/windows/windowslive/messenger.aspx

Re: Help needed to buid GCC for NEC V850

[Kai Ruottu]

gowrisankar loganathan wrote:

> $ make
>  
> now I got the error as 
>  
> gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../Gcc_Source/gcc-4.3.3/libiberty/../incl
> ude  -W -Wall -Wwrite-strings -Wstrict-prototypes -pedantic  ../../Gcc_Source/gc
> c-4.3.3/libiberty/pex-unix.c -o pex-unix.o
<snip>
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_unix_fdopenw':
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: warning: implicit declarati
> on of function `fcntl'
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `F_SETFD' undeclared
>  (first use in this function)
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: (Each undeclared ide
> ntifier is reported only once
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: for each function it
>  appears in.)
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `FD_CLOEXEC' undecla
> red (first use in this function)
>  
> Can any one help me to fix the issue.

Just look in which standard C headers for Cygwin these are now
declared, if in any... Then why this headers wasn't seen in the
libiberty/configure. The '$build/libiberty/config.log' should
give some hint...


My old Cygwin toolchain had these in 'sys/fcntl.h'...

RE: Help needed to buid GCC for NEC V850

[gowrisankar loganathan]

Thanks for the information, but I didn't find the file fcntl.h in the downloaded package, I used gcc-core-4.3.3.tar.bz2
Also I searched for the definition 'FD_CLOEXEC' I didn't find this from any of the files.
 
With Thanks & Regard,
Gowrisankar Loganathan

----------------------------------------
> Date: Mon, 16 Mar 2009 16:28:23 +0200
> From: kai.ruottu@wippies.com
> To: lgowris@hotmail.com
> CC: gcc-help@gcc.gnu.org
> Subject: Re: Help needed to buid GCC for NEC V850
>
> gowrisankar loganathan wrote:
>
>> $ make
>>
>> now I got the error as
>>
>> gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../Gcc_Source/gcc-4.3.3/libiberty/../incl
>> ude -W -Wall -Wwrite-strings -Wstrict-prototypes -pedantic ../../Gcc_Source/gc
>> c-4.3.3/libiberty/pex-unix.c -o pex-unix.o
> 
>> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_unix_fdopenw':
>> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: warning: implicit declarati
>> on of function `fcntl'
>> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `F_SETFD' undeclared
>> (first use in this function)
>> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: (Each undeclared ide
>> ntifier is reported only once
>> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: for each function it
>> appears in.)
>> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `FD_CLOEXEC' undecla
>> red (first use in this function)
>>
>> Can any one help me to fix the issue.
>
> Just look in which standard C headers for Cygwin these are now
> declared, if in any... Then why this headers wasn't seen in the
> libiberty/configure. The '$build/libiberty/config.log' should
> give some hint...
>
>
> My old Cygwin toolchain had these in 'sys/fcntl.h'...
_________________________________________________________________
Twice the fun—Share photos while you chat with Windows Live Messenger.
http://www.microsoft.com/india/windows/windowslive/messenger.aspx

Re: Help needed to buid GCC for NEC V850

[Kai Ruottu]

gowrisankar loganathan wrote:

> Thanks for the information, but I didn't find the file fcntl.h in the downloaded package,
 > I used gcc-core-4.3.3.tar.bz2
> Also I searched for the definition 'FD_CLOEXEC' I didn't find this from any of the files.

The 'gcc' in your log is the Cygwin GCC ! So it uses its own "Cygwin
target headers" when compiling something for Cygwin :

>>> gcc -c -DHAVE_CONFIG_H -g -O2 -I.
 >>> -I../../Gcc_Source/gcc-4.3.3/libiberty/../include

But other headers could be required additionally...

So the 'fcntl.h' should be in your Cygwin target headers in
'/usr/include' or something !

A sanity check :

Can your GCC compile and link anything?  For instance the
famous "Hello World" ?  If you cannot do this, how you
could imagine your compiler to succeed in compiling GCC
from its sources ?

Probably it is possible to download and install only the
GCC part but no headers and no libraries for Cygwin...

RE: Help needed to buid GCC for NEC V850

[gowrisankar loganathan]

I have Mingw in the same PC which compiles all programes corrrectly. 

----------------------------------------
> Date: Mon, 16 Mar 2009 17:22:20 +0200
> From: kai.ruottu@wippies.com
> To: lgowris@hotmail.com
> CC: gcc-help@gcc.gnu.org
> Subject: Re: Help needed to buid GCC for NEC V850
>
> gowrisankar loganathan wrote:
>
>> Thanks for the information, but I didn't find the file fcntl.h in the downloaded package,
>> I used gcc-core-4.3.3.tar.bz2
>> Also I searched for the definition 'FD_CLOEXEC' I didn't find this from any of the files.
>
> The 'gcc' in your log is the Cygwin GCC ! So it uses its own "Cygwin
> target headers" when compiling something for Cygwin :
>
>>>> gcc -c -DHAVE_CONFIG_H -g -O2 -I.
>>>> -I../../Gcc_Source/gcc-4.3.3/libiberty/../include
>
> But other headers could be required additionally...
>
> So the 'fcntl.h' should be in your Cygwin target headers in
> '/usr/include' or something !
>
> A sanity check :
>
> Can your GCC compile and link anything? For instance the
> famous "Hello World" ? If you cannot do this, how you
> could imagine your compiler to succeed in compiling GCC
> from its sources ?
>
> Probably it is possible to download and install only the
> GCC part but no headers and no libraries for Cygwin...
_________________________________________________________________
So many new options, so little time. Windows Live Messenger.
http://www.microsoft.com/india/windows/windowslive/messenger.aspx

Re: Help needed to buid GCC for NEC V850

[Kai Ruottu]

gowrisankar loganathan wrote:

> I have Mingw in the same PC which compiles all programes corrrectly. 

What on earth this note has to do with this build problem?

You configured the GCC for Cygwin $host, not for MinGW $host
('i686-mingw32'). So you MUST have the Cygwin GCC as the 'gcc'
which compiles the GCC sources !

>> The 'gcc' in your log is the Cygwin GCC ! So it uses its own "Cygwin
>> target headers" when compiling something for Cygwin :
>>
>>>>> gcc -c -DHAVE_CONFIG_H -g -O2 -I.
>>>>> -I../../Gcc_Source/gcc-4.3.3/libiberty/../include
>> But other headers could be required additionally...
>>
>> So the 'fcntl.h' should be in your Cygwin target headers in
>> '/usr/include' or something !

Very simply: If you want the 'v850-elf' target GCC for the
Cygwin $host, then use the Cygwin target GCC with its headers
and libraries! If you want the 'v850-elf' target GCC for the
MinGW $host, then please use the MinGW target GCC with its
headers and libraries! And in this MinGW case also use the
'--host=i686-mingw32' when configuring the GCC...

Gcc for V850

[gowrisankar loganathan]

Hello All,
            I build the tool chain for v850 with following command
 
$ ../../gcc_source/gcc-4.3.0/configure --target=v850-elf -prefix=/tools --exec-
prefix=/tools/Gnu-i686-V850 --with-gnu-as --with-gnu-ld --with-newlib -v 2>&1 |
 tee configure.out
 
$ make -w all-gcc install-gcc LANGUAGE="c c++" 2>&1 | tee make.out
 
 
and then try to compile test file as follows
 

$ v850-elf-gcc  -Wall  test.c -o test
test.c: In function 'main':
test.c:16: warning: 'return' with no value, in function returning non-void
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s: Assembler messages:
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Warning: .type pseudo-
op used outside of .def/.endef ignored.
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Error: junk at end of
line, first unrecognized character is `_'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:7: Error: too many memory
 references for `add'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:8: Error: no such instruc
tion: `st.w r29,12[sp]'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:9: Error: too many memory
 references for `mov'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:10: Error: no such instru
ction: `st.w r0,4[r29]'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:11: Error: too many memor
y references for `mov'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:12: Error: no such instru
ction: `st.w r10,8[r29]'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:13: Error: no such instru
ction: `ld.w 4[r29],r11'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:14: Error: no such instru
ction: `ld.w 8[r29],r10'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:15: Error: too many memor
y references for `cmp'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:16: Error: no such instru
ction: `be .L4'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:17: Error: no such instru
ction: `movea lo(20),r0,r10'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:18: Error: no such instru
ction: `st.w r10,8[r29]'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:20: Error: too many memor
y references for `mov'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:21: Error: no such instru
ction: `ld.w 12[sp],r29'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:22: Error: no such instru
ction: `addi 16,sp,sp'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:23: Error: invalid char '
[' beginning operand 1 `[r31]'
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:24: Warning: .size pseudo
-op used outside of .def/.endef ignored.
/cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:24: Error: junk at end of
 line, first unrecognized character is `_'

I didn't get any clue where to look for these error, can anyone provide some info 
 
 
with Thanks & Regards,
Gowrisankar Loganathan
_________________________________________________________________
The new Windows Live Messenger. You don’t want to miss this.
http://www.microsoft.com/india/windows/windowslive/messenger.aspx

Re: Gcc for V850

[Jeff Law]

gowrisankar loganathan wrote:
> Hello All,
>             I build the tool chain for v850 with following command
>  
> $ ../../gcc_source/gcc-4.3.0/configure --target=v850-elf -prefix=/tools --exec-
> prefix=/tools/Gnu-i686-V850 --with-gnu-as --with-gnu-ld --with-newlib -v 2>&1 |
>  tee configure.out
>  
> $ make -w all-gcc install-gcc LANGUAGE="c c++" 2>&1 | tee make.out
>  
>  
> and then try to compile test file as follows
>   
[ ... ]

>  
>
> $ v850-elf-gcc  -Wall  test.c -o test
> test.c: In function 'main':
> test.c:16: warning: 'return' with no value, in function returning non-void
> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s: Assembler messages:
>   
Note it says "assembler messages".  Have you built and installed a v850 
assembler?
jeff

Re: Gcc for V850

[Ian Lance Taylor]

gowrisankar loganathan <lgowris@hotmail.com> writes:

> $ v850-elf-gcc  -Wall  test.c -o test
> test.c: In function 'main':
> test.c:16: warning: 'return' with no value, in function returning non-void
> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s: Assembler messages:
> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Warning: .type pseudo-
> op used outside of .def/.endef ignored.
> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Error: junk at end of
> line, first unrecognized character is `_'

Most likely you are using an x86 assembler rather than a v850 assembler.
Use the -v option to see which assembler is being run.  You must ensure
that that is a v850 assembler.

Ian

RE: Gcc for V850

[gowrisankar loganathan]

The configuration indiates it is using gnu assembler and loader, the below is the configuration
 
$ v850-elf-gcc  -v
Using built-in specs.
Target: v850-elf
Configured with: ../../gcc_source/gcc-4.3.0/configure --target=v850-elf -prefix=
/tools --exec-prefix=/tools/Gnu-i686-V850 --with-gnu-as --with-gnu-ld --with-new
lib -v
Thread model: single
gcc version 4.3.0 (GCC)

----------------------------------------
> To: lgowris@hotmail.com
> CC: gcc-help@gcc.gnu.org
> Subject: Re: Gcc for V850
> From: iant@google.com
> Date: Thu, 19 Mar 2009 16:23:30 -0700
>
> gowrisankar loganathan writes:
>
>> $ v850-elf-gcc -Wall test.c -o test
>> test.c: In function 'main':
>> test.c:16: warning: 'return' with no value, in function returning non-void
>> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s: Assembler messages:
>> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Warning: .type pseudo-
>> op used outside of .def/.endef ignored.
>> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Error: junk at end of
>> line, first unrecognized character is `_'
>
> Most likely you are using an x86 assembler rather than a v850 assembler.
> Use the -v option to see which assembler is being run. You must ensure
> that that is a v850 assembler.
>
> Ian
_________________________________________________________________
So many new options, so little time. Windows Live Messenger.
http://www.microsoft.com/india/windows/windowslive/messenger.aspx

Re: Gcc for V850

[Kai Ruottu]

gowrisankar loganathan wrote:

> The configuration indiates it is using gnu assembler and loader, the below is the configuration
>  
> $ v850-elf-gcc  -v
> Using built-in specs.
> Target: v850-elf
> Configured with: ../../gcc_source/gcc-4.3.0/configure --target=v850-elf -prefix=
> /tools --exec-prefix=/tools/Gnu-i686-V850 --with-gnu-as --with-gnu-ld --with-new
> lib -v
> Thread model: single
> gcc version 4.3.0 (GCC)

Of course v850 has different machine language from x86, the ELF object
format is different from the COFF-based PE format in Cygwin/x86 etc. So
different directives in assembly made for ELF format will not be
understood by a PE-format assembler...

The GNU assembler will be configured for only one CPU (family), in this
case it should be configured and built for the same 'v850-elf' target as
the GCC...

What else you have forgotten to produce?  Have you any C-library ?  The
'--with-newlib' says that you are going to use the 'newlib' as this and
when one cannot produce even a "Hello World" application for the target
without a C library, then maybe you would like to have that... Maybe
also a debugger/simulator like GDB for 'v850-elf' could be useful...

RE: Gcc for V850

[gowrisankar loganathan]

I am finding the assembler and loader for the V850 has not been generated (I didn't find V50-elf-as or V50-elf-ld) in the target directory, what will be the correct configuration to generate this.
 
 
Gowrisankar 

----------------------------------------
> To: lgowris@hotmail.com
> CC: gcc-help@gcc.gnu.org
> Subject: Re: Gcc for V850
> From: iant@google.com
> Date: Thu, 19 Mar 2009 16:23:30 -0700
>
> gowrisankar loganathan writes:
>
>> $ v850-elf-gcc -Wall test.c -o test
>> test.c: In function 'main':
>> test.c:16: warning: 'return' with no value, in function returning non-void
>> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s: Assembler messages:
>> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Warning: .type pseudo-
>> op used outside of .def/.endef ignored.
>> /cygdrive/c/DOKUME~1/SECOND~1/LOKALE~1/Temp/ccI33e2q.s:5: Error: junk at end of
>> line, first unrecognized character is `_'
>
> Most likely you are using an x86 assembler rather than a v850 assembler.
> Use the -v option to see which assembler is being run. You must ensure
> that that is a v850 assembler.
>
> Ian
_________________________________________________________________
The new Windows Live Messenger. You don’t want to miss this.
http://www.microsoft.com/india/windows/windowslive/messenger.aspx

Re: Gcc for V850

[Ian Lance Taylor]

gowrisankar loganathan <lgowris@hotmail.com> writes:

> The configuration indiates it is using gnu assembler and loader, the below is the configuration
>  
> $ v850-elf-gcc  -v
> Using built-in specs.
> Target: v850-elf
> Configured with: ../../gcc_source/gcc-4.3.0/configure --target=v850-elf -prefix=
> /tools --exec-prefix=/tools/Gnu-i686-V850 --with-gnu-as --with-gnu-ld --with-new
> lib -v
> Thread model: single
> gcc version 4.3.0 (GCC)

That unfortunately doesn't mean very much.  You have to actually compile
something and see which assembler is actually run.

v850-elf-gcc -v -c foo.c

Ian

Re: Gcc for V850

[Ian Lance Taylor]

gowrisankar loganathan <lgowris@hotmail.com> writes:

> I am finding the assembler and loader for the V850 has not been
> generated (I didn't find V50-elf-as or V50-elf-ld) in the target
> directory, what will be the correct configuration to generate this.

You need the GNU binutils.  http;//sourceware.org/binutils/

You may also need a C library and a debugger.  gcc is only a compiler,
nothing else.

Ian