This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Artem Alimarine wrote: > > Hello, > > Has anyone managed to build gcc for vxworks5.1? How? > > In my case it fixes the system includes in such a way that the compiling > of libgcc fails. > Perhaps there is a way to tell the make not to fix includes. > > target=i960-wrs-vxworks5.1 > $src/configure \ > --target=$target \ > --prefix=$rel \ > --enable-languages=c,c++ \ > --with-gnu-ld \ > --with-gnu-as my config that worked (for linux and similar for sunos) on VxWorks 5.1 m68k was as follows: export build_base=/tmp export host=i586-pc-linux export target=m68k-wrs-vxworks export prefix=$build_base/gnu_utils/linux2_68k_cross export i=$prefix/bin export PARALLELMFLAGS=-j2 export PATH=$PATH cd build-binutils ../binutils-2.9.1/configure --host=$host --target=$target --prefix=$prefix -v make $PARALLELMFLAGS all echo 'it does not seem to get done on the first go around, so do it again.' make all make $PARALLELMFLAGS install cd ../build-gcc ../gcc-2.8.1/configure --host=$host --target=$target --prefix=$prefix -v make $PARALLELMFLAGS LANGUAGES=c make $PARALLELMFLAGS install LANGUAGES=c Note: I had placed just the VxWorks headers, from the OLD supplied gcc, in $prefix/include just before starting the build. This produced the binutils and gcc binaries I have used for about a year now. Also, on comp.os.vxworks from what I remember of reading it, there seemed to be some tricks you have to play to use C++ on VxWorks, so I would suggest thinking twice about using C++ with VxWorks. > > If it matters, I am compiling on Cygwin > don't know but I doubt it, however most times I hear people talk about building compilers for the MS platform they do the canadian cross thing from some unix platform. <SNIP> > Compile for i960-unknown-coff with newlib builds fine but then I can not > use vxworks include files. It took me a while to realize this, but you do not need newlib. your c library is built into the VxWorks kernel. > > Any help is appreciated, > Artem > > ---------------------------------------------------------------------------------- > ------ > 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |