This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.4 make install problem
On Tue, Jan 28, 2003 at 05:42:30PM +0100, Christian Cornelssen wrote:
> > ~ > cd gcc
> > ~ > ./configure --prefix=/usr/local --enable-languages=c,c++ --disable-nls
> Hmm, no VPATH build...
> > 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.
that works
> Anyway, the non-update of srcdir is clearly a bug,
without ever having a look at gcc's configure/makfile-scripts - that
shouldn't be too hard to fix (if the wrong path to mkinstalldirs is
the only problem)
> but probably a known one, that's why VPATH building is recommended.
Sure I can use that in the future. JFTR, the "old fashioned way"
stopped working with gcc 3.4 about ~2-3 weeks ago.
urs