public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
* kind of cross compiling howto
@ 2000-05-31  8:33 Stephane Dalton
  2000-05-31  8:49 ` Andy
  2000-06-01  4:57 ` Roger Racine
  0 siblings, 2 replies; 7+ messages in thread
From: Stephane Dalton @ 2000-05-31  8:33 UTC (permalink / raw)
  To: crossgcc

Hi there,

Here's a first draft of a document I'm writing about cross compiling using
gnu tools, it's far from being complete and it might contains errors.  I've
taken the example of generating a cross compiler for m68k on a intel (i586)
machine. But a lot of these might also be applied to any target/host
configuration, so one might want to look at it before posting on the mailing
list!

For any suggestions, improvements corrections or comments you can contact
me, I'll try to answer questions to the best of my knowledge and find the
most accurate information possible but please be aware that I'm not an
expert, I'm just trying to group the knowledge available together in the
hope that it will help people.

Thanks

 <<gccm68k.txt>> 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kind of cross compiling howto
  2000-05-31  8:33 kind of cross compiling howto Stephane Dalton
@ 2000-05-31  8:49 ` Andy
  2000-06-01  4:57 ` Roger Racine
  1 sibling, 0 replies; 7+ messages in thread
From: Andy @ 2000-05-31  8:49 UTC (permalink / raw)
  To: crossgcc

Thanks for doing this.. It will save a lot of people time and frustration :-))

It is my understanding that newlib is used mostly for cross-compilers for
embedded OS's - what about a cross compiler for a desktop OS  - what do you
use instead ? libc?
TIA andy

>Hi there,
>
>Here's a first draft of a document I'm writing about cross compiling using
>gnu tools, it's far from being complete and it might contains errors.  I've
>taken the example of generating a cross compiler for m68k on a intel (i586)
>machine. But a lot of these might also be applied to any target/host
>configuration, so one might want to look at it before posting on the mailing
>list!
>
>For any suggestions, improvements corrections or comments you can contact
>me, I'll try to answer questions to the best of my knowledge and find the
>most accurate information possible but please be aware that I'm not an
>expert, I'm just trying to group the knowledge available together in the
>hope that it will help people.
>
>Thanks
>
> <<gccm68k.txt>>
>
>Attachment converted: MacGeek:gccm68k.txt (TEXT/ttxt) (0002CA5E)
>------
>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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kind of cross compiling howto
  2000-05-31  8:33 kind of cross compiling howto Stephane Dalton
  2000-05-31  8:49 ` Andy
@ 2000-06-01  4:57 ` Roger Racine
  1 sibling, 0 replies; 7+ messages in thread
From: Roger Racine @ 2000-06-01  4:57 UTC (permalink / raw)
  To: Stephane Dalton, crossgcc

Have you looked at the web site
http://www.objsw.com/CrossGCC/FAQ-4.html#ss4.1

("How to configure, build, and install GCC as a cross-compiler")?

Roger Racine

At 11:32 AM 5/31/2000 , Stephane Dalton wrote:
>Hi there,
>
>Here's a first draft of a document I'm writing about cross compiling using
>gnu tools, it's far from being complete and it might contains errors.  I've
>taken the example of generating a cross compiler for m68k on a intel (i586)
>machine. But a lot of these might also be applied to any target/host
>configuration, so one might want to look at it before posting on the mailing
>list!
>
>For any suggestions, improvements corrections or comments you can contact
>me, I'll try to answer questions to the best of my knowledge and find the
>most accurate information possible but please be aware that I'm not an
>expert, I'm just trying to group the knowledge available together in the
>hope that it will help people.
>
>Thanks
>
>  <<gccm68k.txt>>
>
>------
>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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kind of cross compiling howto
@ 2001-04-24  4:53 Nabil Ahami
  0 siblings, 0 replies; 7+ messages in thread
From: Nabil Ahami @ 2001-04-24  4:53 UTC (permalink / raw)
  To: crossgcc

I try to compile a cross compiler on Linux/i686/pc for
target powerpc-elf.
How can i modify the spec file?

The following code is for m68k-elf, what is about
powerpc-elf?
------ snip ----------
*link:
-m m68kelf -T bcc.ld%s

*lib:
-lc -lbcc -lc

*libgcc:
-lgcc

*startfile:

------ snip ----------
thank u!


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kind of cross compiling howto
@ 2000-06-03  4:31 Frank Meurer
  0 siblings, 0 replies; 7+ messages in thread
From: Frank Meurer @ 2000-06-03  4:31 UTC (permalink / raw)
  To: crossgcc; +Cc: Germain Ivanoff-Trinadtzaty

As I mentioned a time ago I wrote a quick'n'dirty HOWTO
(especially for my own usage ;-) ). It covers the building
of a i386->m68k xgcc for linux. Maybe it can help someone
to jump over some pitfalls.
Please look at:

   http://www-fs.nt.fh-koeln.de:8080/m68k/


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kind of cross compiling howto
@ 2000-06-02  4:53 John Smith
  0 siblings, 0 replies; 7+ messages in thread
From: John Smith @ 2000-06-02  4:53 UTC (permalink / raw)
  To: crossgcc, Stephane.Dalton

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

My cygwin is 1.1.0 (with cygwin-20000301.tar.gz) 
under windows 2K. My mounts are : bash-2.03$ 
mount Device              
Directory           
Type         
Flags d:\cygwin\bin       
/usr/bin            
user         
binmode d:\cygwin\lib       
/usr/lib            
user         
binmode d:\cygwin           
/                   
user         
textmode bash-2.03$ I'm trying to build a crossgcc cygwin X m68k-coff 
for several weeks. I read read your <gccm68k.txt> with great interest, and 
tried to make it the way you explain. Helas ... - I could build binutils 
2.9.1 (and also binutils-19990818 from 
mirror/cygwin/latest/binutils/binutils-19990818-1-src.tar.gz) - Then I 
provide THIS symlink : bash-2.03$ cd 
/usr/local/m68k-coff bash-2.03$ ln -s 
/usr/local/src/newlib-1.8.2/newlib/libc/include 
sys-include                                                                  
^^^^^^^^^^^ because if I create a symlink called include, building gcc 
fails, saying : can't cd to m68k-coff/sys-include. Am I right ? - BUT I 
STILL CANNOT build gcc 2.95.2 ; here is error messages : bash-2.03$ make 
> mymake.log ../../gcc-2.95.2-1/libiberty/pexecute.c: In function 
`pexecute': ../../gcc-2.95.2-1/libiberty/pexecute.c:418: warning: assignment 
discards qualifiers from pointer target type ../../gcc-2.95.2-1/gcc/gcc.c: In 
function `process_command': ../../gcc-2.95.2-1/gcc/gcc.c:2897: warning: 
passing arg 3 of `make_relative_prefix' discards qualifiers from pointer target 
type ../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c: In function 
`initialize': ../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c:349: `SIGIOT' 
undeclared (first use in this 
function) ../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c:349: (Each undeclared 
identifier is reported only 
once ../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c:349: for each function it 
appears in.) make[2]: *** [fixincl.o] Error 
1 ../../gcc-2.95.2-1/gcc/libgcc1-test.c:101: warning: conflicting types for 
built-in function `memcpy' cxxmain.c: In function `main': cxxmain.c:4527: 
warning: assignment discards qualifiers from pointer target 
type cxxmain.c:4530: warning: assignment discards qualifiers from pointer 
target type ../../gcc-2.95.2-1/gcc/cpp.texi: error 0 make[1]: *** 
[cpp.info] Error 2 make: *** [all-gcc] Error 2 bash-2.03 => make 
breaks before building m68k-coff-gcc So could you please tell me 
: - what is your version of cygwin ? - what are your mounts 
? - what version of gcc do you use ? I meam : where did you get the 
archive ?   There several versions whose name is prefixed by 
gcc-2.95.2, depending on the site from where you downloaded it.   Is 
there any patches to apply against gcc, to fix fixincl.c ? - Am I doing 
right for the symlink ?
- Libiberty is built within binutils. Is it 
necessary to rebuild it within gcc package ? If not, how can I avoid this 
?
 
 
Thank you very 
much, Germain Ivanoff-Trinadtzaty
 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kind of cross compiling howto
  2000-05-23  8:25 gdb + 68360 + bdm Stephane Dalton
@ 2000-06-02  3:13 ` Germain Ivanoff-Trinadtzaty
  0 siblings, 0 replies; 7+ messages in thread
From: Germain Ivanoff-Trinadtzaty @ 2000-06-02  3:13 UTC (permalink / raw)
  To: Stephane Dalton, crossgcc

My cygwin is 1.1.0 (with cygwin-20000301.tar.gz) under windows 2K. My mounts are :

bash-2.03$ mount
Device              Directory           Type         Flags
d:\cygwin\bin       /usr/bin            user         binmode
d:\cygwin\lib       /usr/lib            user         binmode
d:\cygwin           /                   user         textmode
bash-2.03$

I'm trying to build a crossgcc cygwin X m68k-coff for several weeks. I read read your <gccm68k.txt> with great interest, and tried to make it the way you explain. Helas ...

- I could build binutils 2.9.1 (and also binutils-19990818 from mirror/cygwin/latest/binutils/binutils-19990818-1-src.tar.gz)

- Then I provide THIS symlink :

bash-2.03$ cd /usr/local/m68k-coff

bash-2.03$ ln -s /usr/local/src/newlib-1.8.2/newlib/libc/include sys-include

                                                                 ^^^^^^^^^^^

because if I create a symlink called include, building gcc fails, saying : can't cd to m68k-coff/sys-include. Am I right ?

- BUT I STILL CANNOT build gcc 2.95.2 ; here is error messages :

bash-2.03$ make > mymake.log
../../gcc-2.95.2-1/libiberty/pexecute.c: In function `pexecute':
../../gcc-2.95.2-1/libiberty/pexecute.c:418: warning: assignment discards qualifiers from pointer target type
../../gcc-2.95.2-1/gcc/gcc.c: In function `process_command':
../../gcc-2.95.2-1/gcc/gcc.c:2897: warning: passing arg 3 of `make_relative_prefix' discards qualifiers from pointer target type
../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c: In function `initialize':
../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c:349: `SIGIOT' undeclared (first use in this function)
../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c:349: (Each undeclared identifier is reported only once
../../../gcc-2.95.2-1/gcc/fixinc/fixincl.c:349: for each function it appears in.)
make[2]: *** [fixincl.o] Error 1
../../gcc-2.95.2-1/gcc/libgcc1-test.c:101: warning: conflicting types for built-in function `memcpy'
cxxmain.c: In function `main':
cxxmain.c:4527: warning: assignment discards qualifiers from pointer target type
cxxmain.c:4530: warning: assignment discards qualifiers from pointer target type
../../gcc-2.95.2-1/gcc/cpp.texi: error 0
make[1]: *** [cpp.info] Error 2
make: *** [all-gcc] Error 2
bash-2.03

=> make breaks before building m68k-coff-gcc

So could you please tell me :

- what is your version of cygwin ?

- what are your mounts ?

- what version of gcc do you use ? I meam : where did you get the archive ?

  There several versions whose name is prefixed by gcc-2.95.2, depending on the site from where you downloaded it.

  Is there any pathes to apply against gcc, to fix fixincl.c ?

- Am I doing right for the symlink ?

Thank you very much,

Germain Ivanoff-Trinadtzaty




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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2001-04-24  4:53 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-05-31  8:33 kind of cross compiling howto Stephane Dalton
2000-05-31  8:49 ` Andy
2000-06-01  4:57 ` Roger Racine
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24  4:53 Nabil Ahami
2000-06-03  4:31 Frank Meurer
2000-06-02  4:53 John Smith
2000-05-23  8:25 gdb + 68360 + bdm Stephane Dalton
2000-06-02  3:13 ` kind of cross compiling howto Germain Ivanoff-Trinadtzaty

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).