This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: problem cross-compiling gcc 3.4.3 from x86/linux to


Roberto Fichera wrote:

At 21.09 31/01/2005, Daniel Jacobowitz wrote:

On Mon, Jan 31, 2005 at 09:06:03PM +0100, jf wrote:
> Roberto Fichera wrote:
>
> >Hi Jean-Francois,
> >
> >I've read your post at the gcc-help mailing list about the gcc3.4.3 cross
> >compilation for linux/x86 to PPC604/vxWorks. Currently I've the same
> >error,
> >did you resolve the CPU undefined error in some way?
> >
> >Best regards,
> >
> >Roberto Fichera.
>
> Yes I did !
> I remember it is a problem with multi lib...
> I didn't really solved the problem but If you just plan to use your
> compiler only with ppc604 I've got a dit hack that works fine :
> In the file that cause the error (#error directive) just hard define CPU
> and CPU_FAMILY then run make again....
> let me know if it works (if no I'll have a look deeper into what I did)


IIRC, CPU is normally defined on the command line by the VxWorks
makefiles.  One of many quirks of building compilers for VxWorks.


The first compilation, after untar the gcc package, goes clean if I --enable-languages=c only.
But if I try to recompile after a make install, the compilation fails because fixinclude changes
the VxWorks includes.

sounds like a problem in your path... are you sure your cross-gcc isn't installed first in you path ?



The compilation of the g++ and the gcj goes also clean but I was unable to compile the
libstdc++v3 because I getting these errors below

I previously tried to have C++ support for vxworks... the problem is:
c++ includes provided with vxworks (like list and vector...) are old and buggy (some are 10years old) and are not compatible with the c++ standard. So g++ reject them.
So you might want to delete them and use those provided bu libstdc++ but you'll have to port this lib to vxworks and here are some real issues....for example thread definition are incompatible....
It might be an interesting job but my customer didn't want to pay, so I stopped working on it...



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]