Re: Adding newlib to existing GCC, prefix?

[Jeff Johnston <jjohnstn at redhat dot com>]

Jeff Johnston wrote:
> Vitus Jensen wrote:
>
> > > Vitus Jensen wrote:
> > >
> > > > I'm trying to add newlib-1.12.0 to an existing port of GCC.  That GCC
> > > > was produced some year ago by a collegue no longer available.  He
> > > > used the coldfire project (http://sca.uwaterloo.ca/coldfire/) to
> > > > crosscompile from Windows 2000 (cygwin B20) to our own
> > > > hardware/software plattform which uses Motorola
> > > > DragonBall and a propritary OS. The compiler itself runs fine, it's 
> > > > just
> > > > that now I need a CRT...
> > > >
> > > > "configure" and "make all" complete successfully, but "make install"
> > > > fails :-(
> > > >
> > > > //T/C/coldfire/gcc-m68k                 ; contains
> > > >                                                   ;
> >
> >
> > bin/m68k-coff-gcc.exe etc
> >
> > > > //T/C/coldfire/newlib-1.12.0             ; contains original
> > > >                                                   ; newlib1.12.0
> > > > //T/C/coldfire/newlib                      ; my build directory
> > > >
> > > > I'm using the following configure command (with variations of --host 
> > > > and
> > > > --prefix values):
> > > >
> > > > //T/C/coldfire/newlib-1.12.0/configure --target m68k-coff
> > > > --enable-target-optspace --prefix=//T/C/coldfire/gcc-m68k
> > > >
> > > > "make install" fails when calling install:
> > > >
> > > > INSTALL - gcc-m68k for Win95/NT Release 6
> > > >
> > > > Usage:
> > > >  install install-directory
> > > >
> > > > This program will install gcc-m68k Release 6
> > > > to the install-directory from the current directory.
> >
> >
> >
> >
> > > You appear to be picking up an install binary that isn't the default
> > > "install" binary for Cygwin (note the message you get).  You might
> > > try reissuing the make install command and overriding it's choice by 
> > > adding INSTALL="xxxx" where
> > > xxxx is the normal Cygwin install.
> >
> >
> >
> > Good tip!
> >
> > Makefile is using /GCC-M68K/BIN/install.exe instead of
> > /CYGWIN-B20/H-I586-CYGWIN32/BIN/install.exe.
> >
> > OK, Makefile fiddling is impossible because this path is written to every
> > single Makefile in the tree.
> >
> > Is it OK to edit config.cache and run config.status to recreate 
> > Makefiles?
> > Or do I have to rerun configure and pass extra options?  I remember 
> > that I
> > have seen "Detecting cygwin... no" on the screen but that message is 
> > logged
> > nowhere.  Should configure detect cygwin?
> >
> > Sorry, but I'm new to this configure stuff (and new to windows but this
> > doesn't count :-).
> >
> > Bye,
> >    Vitus
>
> There are certain flags/variables passed down the make tree.  
> Unfortunately, INSTALL isn't one of them, but you can override MAKE 
> itself and specify the INSTALL override at the same time.  Thus, you can 
> specify:
>
>    make install-target-newlib MAKE="<cygwin's make.exe>" 
> INSTALL=\"<cygwin's install.exe>\""

Oops, extra double-quote in there.  Should be:

make install-target-newlib MAKE="<cygwin's make.exe> INSTALL=\"<cygwin's 
install.exe>\""

You can optionally omit the \" around the install.exe name.

-- Jeff J.

> -- Jeff J.