RE: Promblem compiling GDB 6.3 on solaris 2.6--don't know how to make target doc/observer.texi

["Xing Li Jun, SLC COM TD-SCDMA (BJ)" <lijun.xing@siemens.com>]

> -----Original Message-----
> From: Dave Korn [mailto:dave.korn@artimi.com]
> Sent: Tuesday, January 18, 2005 8:18 PM
> To: 'Xing Li Jun, SLC COM TD-SCDMA (BJ)'; gdb@sources.redhat.com
> Subject: RE: Promblem compiling GDB 6.3 on solaris 2.6--don't 
> know how to make target doc/observer.texi
> 
> 
> > -----Original Message-----
> > From: Xing Li Jun, SLC COM TD-SCDMA (BJ)
> > Sent: 18 January 2005 08:54
> > To: Dave Korn; gdb
> > Subject: RE: Promblem compiling GDB 6.3 on solaris 2.6--don't 
> > know how to make target doc/observer.texi
> > 
> > After some trial and error, I successfully compiled gdb. The 
> > action I've taken
> > is :
> > 1. replace the sun make with gmake
> > 2. run configure with the full path, instead of the relative 
> > path to the build dir.
> > 
> > thank Dave for your information, anyway!
> 
>   I am glad you succeeded.  I think that using GNU make is an absolute
> requirement for building gnu projects where srcdir != objdir, 
> because only gmake
> supports VPATH, not Sun make.  I have heard of problems with 
> using a relative
> instead of absolute path to configure on Sun before, but that 
> was to do with
> gcc; maybe it affects gdb as well.
> 
> 
>     cheers, 
>       DaveK

yes, I compiled gdb and gcc on Sun at the same time, and I got the same problem for gcc 3.4.3.
If the configure is run with a relative path, the the path to install-sh will be wrong, an error 'install-sh: not found' will rise. When I got this error  for gdb, I just re-run the configure-make prcess with an absolute path to the configure script, and succeed. 
But for gcc, the make process take so  long that I can not afford the time re-compile it, so I mkdir a gcc-3.4.3, with only install-sh into it, then I copy this directory everywhere to let the make can find it:)

cheers,
Xing Li Jun


> -- 
> Can't think of a witty .sigline today....
>