From: "Xing Li Jun, SLC COM TD-SCDMA (BJ)" <lijun.xing@siemens.com>
To: Dave Korn <dave.korn@artimi.com>, 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
Date: Wed, 19 Jan 2005 01:15:00 -0000 [thread overview]
Message-ID: <AF8D5638D08F2348ADD61E563A8989C8044E7E3F@pekw091a> (raw)
> -----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....
>
next reply other threads:[~2005-01-19 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 1:15 Xing Li Jun, SLC COM TD-SCDMA (BJ) [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 8:54 Xing Li Jun, SLC COM TD-SCDMA (BJ)
2005-01-18 12:21 ` Dave Korn
2005-01-17 2:27 Xing Li Jun, SLC COM TD-SCDMA (BJ)
2005-01-14 8:47 Xing Li Jun, SLC COM TD-SCDMA (BJ)
2005-01-14 15:37 ` Dave Korn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AF8D5638D08F2348ADD61E563A8989C8044E7E3F@pekw091a \
--to=lijun.xing@siemens.com \
--cc=dave.korn@artimi.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).