RE: Building gcc 9.95.2 toolchain to run vxWorks on a PowerPC

[David Korn <dkorn at pixelpower dot com>]

>-----Original Message-----
>From: Lovett, Stuart [mailto:Stuart.Lovett@marconi.com]
>Sent: 23 August 2000 22:22
>To: 'help-gcc@gnu.org'
>Subject: RE: Building gcc 9.95.2 toolchain to run vxWorks on a PowerPC
>
>
>Thanks again Dave, I've downloaded version 2.10 and that seems 
>to have fixed
>binutils.  Not surprisingly though, gcc fails when building the file
>'gcc-2.95.2/libio/iovfprintf.c'.  It fails because the vxWorks 
>header file
>'arch/ppc/toolPpc.h' is defining the macro '_STDARG_H' before 
>the header
>file <stdarg.h> is included and thus prevents the 'va_arg' 
>macro from being
>defined.  Without this macro being defined the compiler 
>attempts to compile
>'va_arg(ar, int)' and complains about the int keyword in a 
>strange place.
>
>Can you think of any reason why I am having problems like this?  I am
>following the basic build instructions, ie 'configure, build 
>all, install'
>for binutils then do the same for gcc.  The process is failing 
>during build
>all for gcc.  Do I need to set up any paths or env variables 
>to point the
>process in the right direction?
>
>I had to add <install_dir>/bin to the path at one point since 
>a part of the
>process couldn't find the 'powerpc-wrs-vxworks-ar' tool.  The 
>configure line
>I used for the compiler is:
>
>../gcc/gcc.2.95.2/configure --target=powerpc-wrs-vxworks
>--prefix=/us/slovett/compilers/install_new
>--with-headers=/us/vxdist/5.4/target/h --enable-languages=c++
>--enable-version-specific-runtime-libs -v
>
>then did make all.
>
>Shouldn't the --prefix tell the gcc make process where the 
>binutils are?
>
>Any suggestions?
>
>Thanks,
>
>Stu.

       Hi Stuart,

  Yet again my mail doesn't seem to have made it through to the list. 
This is probably due to my work using PSInet for our ISP; the psinet
smtp server we use is on at least one of the anti-spam blacklists that
Gnu check incoming mail for the mailing lists against, so please pass
on my apologies to the list for only including them in one half of the
conversation!

  Anyway, in answer to your questions, and starting at the end first:
you do indeed need to have $prefix/bin (normally /usr/local/bin, but
in your case /us/slovett/compilers/install_new/bin) in your path; as 
/usr/local/bin is in most people's path settings by default on pretty
much every *nix implementation there is, the build doesn't mess around
with the paths. AFAIK, the --prefix option is only used to tell the
build process where the final files should be installed. So set it in
your $PATH and forget about it; that's ok.

  As far as the actual gcc build itself goes, you're probably doing
fine, although it may not seem that way! The various subdirectories
off the main gcc-2.95.2 directory (libiberty, libio etc) are related
stuff that goes into the C library of the compiler. Since all C library
functionality in VxWorks is already build into the OS, there's no need
to build them at all! It's a slight bug that the build process even
tries, but not a serious one. The solution to your problem is simply
to cd into the gcc subdir from the gcc-2.95.2 dir, and execute your
make all install command there! That way only the crosscompiler itself
is built and installed. Hopefully that should then all work fine.

     hth,
         DaveK
-- 
Event being observed is indistinguishable from the observer.
	-- Schrödinger's cat 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************