gcc 3.4 make install problem

[Christian Cornelssen]

Hello,

On Tue, 28 Jan 2003, urs wrote:

> for about ~2 weeks now the instalation of gcc 3.4 fails due to wrong
> path to (or a missing copy of) mkinstalldirs. below is a sample
> compile session:
> [...]
> ~ > cvs -z 9 co gcc 2>&1
> cvs server: Updating gcc
> [...]
> ~ > cd gcc
> ~ > ./configure --prefix=/usr/local --enable-languages=c,c++ --disable-nls

Hmm, no VPATH build...

> ~ > su
> Password:

Just a note: For mere testing, you can now try setting DESTDIR...

> ~ # make install
> [...]
> make[2]: Leaving directory
> /home/ws/urs/gcc/i686-pc-linux-gnu/libiberty'
> /bin/sh ./../mkinstalldirs /usr/local/lib
> ./../mkinstalldirs: ./../mkinstalldirs: No such file or directory
> make[1]: *** [install_to_libdir] Error 127
> make[1]: Leaving directory /home/ws/urs/gcc/i686-pc-linux-gnu/libiberty'
> make: *** [install-target-libiberty] Error 2

You have srcdir=. and that is wrong.  (${srcdir} should point to the
directory holding libiberty's `Makefile.in'.)  After bootstrapping,
the libraries are built in i686-pc-linux-gnu/, hence srcdir should be
updated to .., but it isn't.

Workaround: Call the toplevel configure from another (clean) working
directory, i.e. do a VPATH build.  Anyway, the non-update of srcdir is
clearly a bug, but probably a known one, that's why VPATH building is
recommended.

Regards,

Christian Cornelssen