FW:

FW:

[Mahadev K Cholachagudda]

Hello all,

	I want to compile and build the gcc ( cross compiler) for m68k-coff on
Linux.
	I successfully built the cross compiler by using the FAQ provided by the
www.obsw.com and running the shell script. But i want to build the tools one
by one and I got the errors as below.

	I performed the following.

/home/kc> mkdir build-bin
/home/kc> cd build-bin
/home/kc/build-bin>
../binutils-2.9.1/configure --target=m68k-coff --prefix=/home/kc/gnu-tools

....
/home/kc/build-bin> make all install
/home/kc/build-bin> mkdir ../build-gcc
/home/kc/build-bin> cd ../build-gcc
/home/kc/build-bin>
../gcc-2.95.2/configure --target=m68k-coff --prefix=/home/kc/gnu-tools --wit
h-local-prefix=/home/kc/gnu-tools --with-newlib --enable-languages="c"

..... successfully

/home/kc/build-bin> make all install
:
:
../../gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file or directory
../../gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file or directory
make[3]: *** [libgcc2.a] Error 1
make[3]: Leaving directory `/home/kc/build-gcc/gcc'
make[2]: *** [stmp-multilib-sub] Error 2
make[2]: Leaving directory `/home/kc/build-gcc/gcc'
make[1]: *** [stmp-multilib] Error 1
make[1]: Leaving directory `/home/kc/build-gcc/gcc'
make: *** [all-gcc] Error 2
/home/kc/build-bin>


Could any one point me where can i get these header files in order to
compile the gcc ?

Thanks for any help

With best regards,

\/ \/   Mahadev K. Cholachagudda
O . O   mailto:kcmahadev@zilogindia.com
 ( )


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re:

[mike]

Hi, Mahadev.
I'm also works with m68k-coff, and succeed build on my windoze.
The problem you got is lack of header files, because gcc needs
them to build libgcc.a. Therefore, get newlib package and put
them in the directory the same as gcc (/home/kc), and run
configure script of gcc again. If you have put newlib in
other directory, it's ok, using
'--with-header=/somewhere/newlib/libc/include' with
configure script of gcc.

----- Original Message -----
From: "Mahadev K Cholachagudda" <kcmahadev@zilogindia.com>
To: "Crossgcc-Help" <crossgcc@sources.redhat.com>
Sent: Friday, January 12, 2001 7:21 PM
Subject: FW:


>
> Hello all,
>
> I want to compile and build the gcc ( cross compiler) for m68k-coff on
> Linux.
> I successfully built the cross compiler by using the FAQ provided by the
> www.obsw.com and running the shell script. But i want to build the tools
one
> by one and I got the errors as below.
>
> I performed the following.
>
> /home/kc> mkdir build-bin
> /home/kc> cd build-bin
> /home/kc/build-bin>
> ../binutils-2.9.1/configure --target=m68k-coff --prefix=/home/kc/gnu-tools
>
> ....
> /home/kc/build-bin> make all install
> /home/kc/build-bin> mkdir ../build-gcc
> /home/kc/build-bin> cd ../build-gcc
> /home/kc/build-bin>
>
../gcc-2.95.2/configure --target=m68k-coff --prefix=/home/kc/gnu-tools --wit
> h-local-prefix=/home/kc/gnu-tools --with-newlib --enable-languages="c"
>
> ..... successfully
>
> /home/kc/build-bin> make all install
> :
> :
> ../../gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file or directory
> ../../gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file or directory
> make[3]: *** [libgcc2.a] Error 1
> make[3]: Leaving directory `/home/kc/build-gcc/gcc'
> make[2]: *** [stmp-multilib-sub] Error 2
> make[2]: Leaving directory `/home/kc/build-gcc/gcc'
> make[1]: *** [stmp-multilib] Error 1
> make[1]: Leaving directory `/home/kc/build-gcc/gcc'
> make: *** [all-gcc] Error 2
> /home/kc/build-bin>
>
>
> Could any one point me where can i get these header files in order to
> compile the gcc ?
>
> Thanks for any help
>
> With best regards,
>
> \/ \/   Mahadev K. Cholachagudda
> O . O   mailto:kcmahadev@zilogindia.com
>  ( )
>
>
> ------
> Want more information?  See the CrossGCC FAQ,
http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to
crossgcc-unsubscribe@sourceware.cygnus.com
>


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

RE: gcc-m68k cross compiler problem gcc2.95.2

[Mahadev K Cholachagudda]

Thanks Mike,
It worked.

But now i have written a sample program to test this.

#include <stdio.h>

int main( void )
{
	printf("\nHello World");
	return 0;
}

When i compile the program  using "m68k-coff-gcc hello.c".
But i got the error as below.

[root@Linux-Test sample]# ../bin/m68k-coff-gcc test.c
/home/kc/gnu-tools/m68k-coff/lib/crt0.o:../../../../newlib-1.8.2/libgloss/m6
8k/c
rt0.S:16: undefined reference to `hardware_init_hook'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x48):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `software_init_hook'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x58):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `__FINI_SECTION__'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x5e):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `atexit'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x64):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `__INIT_SECTION__'
/tmp/ccTN1ZK5.o(.text+0x1e):test.c: undefined reference to `printf'
/home/kc/gnu-tools/lib/gcc-lib/m68k-coff/2.95.2/libgcc.a(_exit.o): In
function `
exit':
/home/kc/build-gcc/gcc/../../gcc-2.95.2/gcc/libgcc2.c(.text+0x12): undefined
ref
erence to `_cleanup'
/home/kc/build-gcc/gcc/../../gcc-2.95.2/gcc/libgcc2.c(.text+0x1a): undefined
ref
erence to `_exit'
collect2: ld returned 1 exit status


What i did was, i wrote a linker script by using the example script. At that
point the entry point is not a main(). I got the appropriate executable.

Can some body tell me how to work around the above problems ?.

I think if i execute gcc to get me the final executable file, the gcc will
intern call pre-processor, c-compiler, assembler and then linker. I think
the linker may not be getting correct linker script or the above definitions
such as (hardware_init_hook etc) are not there in the linker script which ld
is looking for.

Am i correct ?

Thanks for any help,

With best regards,

\/ \/   Mahadev K. Cholachagudda
O . O   mailto:kcmahadev@zilogindia.com
 ( )


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: gcc-m68k cross compiler problem gcc2.95.2

[Pierre Saucourt-Harmel (r54698)]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

Hello,
Mahadev K Cholachagudda wrote:
...
I think if i execute gcc to get me the final executable
file, the gcc will
intern call pre-processor, c-compiler, assembler and then linker. I
think
the linker may not be getting correct linker script or the above definitions
such as (hardware_init_hook etc) are not there in the linker script
which ld
is looking for.
Am i correct ?
Yes, you are.
Just look at the ld.info documentation (part of binutils package) to
study how the linker takes your script and which commands you can use to
write this script.
Your command line to compile should look like that (if your linker
script is named "hello.ld"):
m68k-coff-gcc -Wl,--script=hello.ld hello.c
Moreover, as your gcc compiler do not link with a default C standard
library, I think you did not generate and install correctly the newlib
package.
That's why reference to atexit, printf, _exit and _cleanup symbols
are unresolved.
Your gcc compiler should automatically (without adding any option to
the m68k-coff-gcc invocation) link your executable file with the libc.a
or libg.a.
Check the presence of these libraries under:
<your-installation-directory>/m68k-coff/lib
For __FINI_SECTION__ and __INIT_SECTION__ sections, you should have
defined them into your linker script.
For software_init_hook and harware_init_hook symbols, I don't know.
Regards,
Pierre.
 
 

RE: gcc-m68k cross compiler problem gcc2.95.2

[Mahadev K Cholachagudda]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]

Thanks 
a lot pierre.
mahadev
 

  -----Original Message----- From: 
  crossgcc-owner@sources.redhat.com 
  [mailto:crossgcc-owner@sources.redhat.com] On Behalf Of Pierre 
  Saucourt-Harmel (r54698) Sent: Friday, January 12, 2001 1:44 
  PM To: Mahadev K Cholachagudda Cc: 
  crossgcc@sources.redhat.com Subject: Re: gcc-m68k cross compiler 
  problem gcc2.95.2 Hello, 
  Mahadev K Cholachagudda wrote: ... 
  I think if i execute gcc to get me the final 
    executable file, the gcc will intern call pre-processor, c-compiler, 
    assembler and then linker. I think the linker may not be getting correct 
    linker script or the above definitions such as (hardware_init_hook etc) 
    are not there in the linker script which ld is looking for. 
    Am i correct ? Yes, you are. 
  Just look at the ld.info documentation (part of binutils package) to study 
  how the linker takes your script and which commands you can use to write this 
  script. Your command line to compile should look like that (if your linker 
  script is named "hello.ld"): m68k-coff-gcc -Wl,--script=hello.ld 
  hello.c 
  Moreover, as your gcc compiler do not link with a default C standard 
  library, I think you did not generate and install correctly the newlib 
  package. That's why reference to atexit, printf, _exit and _cleanup 
  symbols are unresolved. 
  Your gcc compiler should automatically (without adding any option to the 
  m68k-coff-gcc invocation) link your executable file with the libc.a or libg.a. 
  Check the presence of these libraries under: 
  <your-installation-directory>/m68k-coff/lib 
  For __FINI_SECTION__ and __INIT_SECTION__ sections, you should have defined 
  them into your linker script. For software_init_hook and harware_init_hook 
  symbols, I don't know. 
  Regards, Pierre.     

RE: gcc-m68k cross compiler problem gcc2.95.2

[Mahadev K Cholachagudda]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]

Thanks 
a lot pierre.
mahadev
 

  -----Original Message----- From: 
  crossgcc-owner@sources.redhat.com 
  [mailto:crossgcc-owner@sources.redhat.com] On Behalf Of Pierre 
  Saucourt-Harmel (r54698) Sent: Friday, January 12, 2001 1:44 
  PM To: Mahadev K Cholachagudda Cc: 
  crossgcc@sources.redhat.com Subject: Re: gcc-m68k cross compiler 
  problem gcc2.95.2 Hello, 
  Mahadev K Cholachagudda wrote: ... 
  I think if i execute gcc to get me the final 
    executable file, the gcc will intern call pre-processor, c-compiler, 
    assembler and then linker. I think the linker may not be getting correct 
    linker script or the above definitions such as (hardware_init_hook etc) 
    are not there in the linker script which ld is looking for. 
    Am i correct ? Yes, you are. 
  Just look at the ld.info documentation (part of binutils package) to study 
  how the linker takes your script and which commands you can use to write this 
  script. Your command line to compile should look like that (if your linker 
  script is named "hello.ld"): m68k-coff-gcc -Wl,--script=hello.ld 
  hello.c 
  Moreover, as your gcc compiler do not link with a default C standard 
  library, I think you did not generate and install correctly the newlib 
  package. That's why reference to atexit, printf, _exit and _cleanup 
  symbols are unresolved. 
  Your gcc compiler should automatically (without adding any option to the 
  m68k-coff-gcc invocation) link your executable file with the libc.a or libg.a. 
  Check the presence of these libraries under: 
  <your-installation-directory>/m68k-coff/lib 
  For __FINI_SECTION__ and __INIT_SECTION__ sections, you should have defined 
  them into your linker script. For software_init_hook and harware_init_hook 
  symbols, I don't know. 
  Regards, Pierre.     

Re: gcc-m68k cross compiler problem gcc2.95.2

[Pierre Saucourt-Harmel (r54698)]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

Hello,
Mahadev K Cholachagudda wrote:
...
I think if i execute gcc to get me the final executable
file, the gcc will
intern call pre-processor, c-compiler, assembler and then linker. I
think
the linker may not be getting correct linker script or the above definitions
such as (hardware_init_hook etc) are not there in the linker script
which ld
is looking for.
Am i correct ?
Yes, you are.
Just look at the ld.info documentation (part of binutils package) to
study how the linker takes your script and which commands you can use to
write this script.
Your command line to compile should look like that (if your linker
script is named "hello.ld"):
m68k-coff-gcc -Wl,--script=hello.ld hello.c
Moreover, as your gcc compiler do not link with a default C standard
library, I think you did not generate and install correctly the newlib
package.
That's why reference to atexit, printf, _exit and _cleanup symbols
are unresolved.
Your gcc compiler should automatically (without adding any option to
the m68k-coff-gcc invocation) link your executable file with the libc.a
or libg.a.
Check the presence of these libraries under:
<your-installation-directory>/m68k-coff/lib
For __FINI_SECTION__ and __INIT_SECTION__ sections, you should have
defined them into your linker script.
For software_init_hook and harware_init_hook symbols, I don't know.
Regards,
Pierre.
 
 

RE: gcc-m68k cross compiler problem gcc2.95.2

[Mahadev K Cholachagudda]

Thanks Mike,
It worked.

But now i have written a sample program to test this.

#include <stdio.h>

int main( void )
{
	printf("\nHello World");
	return 0;
}

When i compile the program  using "m68k-coff-gcc hello.c".
But i got the error as below.

[root@Linux-Test sample]# ../bin/m68k-coff-gcc test.c
/home/kc/gnu-tools/m68k-coff/lib/crt0.o:../../../../newlib-1.8.2/libgloss/m6
8k/c
rt0.S:16: undefined reference to `hardware_init_hook'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x48):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `software_init_hook'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x58):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `__FINI_SECTION__'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x5e):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `atexit'
/home/kc/gnu-tools/m68k-coff/lib/crt0.o(.text+0x64):../../../../newlib-1.8.2
/lib
gloss/m68k/crt0.S: undefined reference to `__INIT_SECTION__'
/tmp/ccTN1ZK5.o(.text+0x1e):test.c: undefined reference to `printf'
/home/kc/gnu-tools/lib/gcc-lib/m68k-coff/2.95.2/libgcc.a(_exit.o): In
function `
exit':
/home/kc/build-gcc/gcc/../../gcc-2.95.2/gcc/libgcc2.c(.text+0x12): undefined
ref
erence to `_cleanup'
/home/kc/build-gcc/gcc/../../gcc-2.95.2/gcc/libgcc2.c(.text+0x1a): undefined
ref
erence to `_exit'
collect2: ld returned 1 exit status


What i did was, i wrote a linker script by using the example script. At that
point the entry point is not a main(). I got the appropriate executable.

Can some body tell me how to work around the above problems ?.

I think if i execute gcc to get me the final executable file, the gcc will
intern call pre-processor, c-compiler, assembler and then linker. I think
the linker may not be getting correct linker script or the above definitions
such as (hardware_init_hook etc) are not there in the linker script which ld
is looking for.

Am i correct ?

Thanks for any help,

With best regards,

\/ \/   Mahadev K. Cholachagudda
O . O   mailto:kcmahadev@zilogindia.com
 ( )


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re:

[mike]

Hi, Mahadev.
I'm also works with m68k-coff, and succeed build on my windoze.
The problem you got is lack of header files, because gcc needs
them to build libgcc.a. Therefore, get newlib package and put
them in the directory the same as gcc (/home/kc), and run
configure script of gcc again. If you have put newlib in
other directory, it's ok, using
'--with-header=/somewhere/newlib/libc/include' with
configure script of gcc.

----- Original Message -----
From: "Mahadev K Cholachagudda" <kcmahadev@zilogindia.com>
To: "Crossgcc-Help" <crossgcc@sources.redhat.com>
Sent: Friday, January 12, 2001 7:21 PM
Subject: FW:


>
> Hello all,
>
> I want to compile and build the gcc ( cross compiler) for m68k-coff on
> Linux.
> I successfully built the cross compiler by using the FAQ provided by the
> www.obsw.com and running the shell script. But i want to build the tools
one
> by one and I got the errors as below.
>
> I performed the following.
>
> /home/kc> mkdir build-bin
> /home/kc> cd build-bin
> /home/kc/build-bin>
> ../binutils-2.9.1/configure --target=m68k-coff --prefix=/home/kc/gnu-tools
>
> ....
> /home/kc/build-bin> make all install
> /home/kc/build-bin> mkdir ../build-gcc
> /home/kc/build-bin> cd ../build-gcc
> /home/kc/build-bin>
>
../gcc-2.95.2/configure --target=m68k-coff --prefix=/home/kc/gnu-tools --wit
> h-local-prefix=/home/kc/gnu-tools --with-newlib --enable-languages="c"
>
> ..... successfully
>
> /home/kc/build-bin> make all install
> :
> :
> ../../gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file or directory
> ../../gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file or directory
> make[3]: *** [libgcc2.a] Error 1
> make[3]: Leaving directory `/home/kc/build-gcc/gcc'
> make[2]: *** [stmp-multilib-sub] Error 2
> make[2]: Leaving directory `/home/kc/build-gcc/gcc'
> make[1]: *** [stmp-multilib] Error 1
> make[1]: Leaving directory `/home/kc/build-gcc/gcc'
> make: *** [all-gcc] Error 2
> /home/kc/build-bin>
>
>
> Could any one point me where can i get these header files in order to
> compile the gcc ?
>
> Thanks for any help
>
> With best regards,
>
> \/ \/   Mahadev K. Cholachagudda
> O . O   mailto:kcmahadev@zilogindia.com
>  ( )
>
>
> ------
> Want more information?  See the CrossGCC FAQ,
http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to
crossgcc-unsubscribe@sourceware.cygnus.com
>


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

FW:

[Mahadev K Cholachagudda]

Hello all,

	I want to compile and build the gcc ( cross compiler) for m68k-coff on
Linux.
	I successfully built the cross compiler by using the FAQ provided by the
www.obsw.com and running the shell script. But i want to build the tools one
by one and I got the errors as below.

	I performed the following.

/home/kc> mkdir build-bin
/home/kc> cd build-bin
/home/kc/build-bin>
../binutils-2.9.1/configure --target=m68k-coff --prefix=/home/kc/gnu-tools

....
/home/kc/build-bin> make all install
/home/kc/build-bin> mkdir ../build-gcc
/home/kc/build-bin> cd ../build-gcc
/home/kc/build-bin>
../gcc-2.95.2/configure --target=m68k-coff --prefix=/home/kc/gnu-tools --wit
h-local-prefix=/home/kc/gnu-tools --with-newlib --enable-languages="c"

..... successfully

/home/kc/build-bin> make all install
:
:
../../gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file or directory
../../gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file or directory
make[3]: *** [libgcc2.a] Error 1
make[3]: Leaving directory `/home/kc/build-gcc/gcc'
make[2]: *** [stmp-multilib-sub] Error 2
make[2]: Leaving directory `/home/kc/build-gcc/gcc'
make[1]: *** [stmp-multilib] Error 1
make[1]: Leaving directory `/home/kc/build-gcc/gcc'
make: *** [all-gcc] Error 2
/home/kc/build-bin>


Could any one point me where can i get these header files in order to
compile the gcc ?

Thanks for any help

With best regards,

\/ \/   Mahadev K. Cholachagudda
O . O   mailto:kcmahadev@zilogindia.com
 ( )


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Fw:

[alexperi]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

I need to read hexadecimal numbers from the 
keyboard
This is my program but as you gather it doesn't 
work.
Need some help. Thanx
file://-----------------------------------------
#include <iostream.h> #include 
<math.h> void main() {  char ch;  int 
x;  cin.setf(ios::hex);  cout.setf(ios::hex);  cin>> 
ch;  cout << ch;
}