From: "Dave Korn" <dave.korn@artimi.com>
To: "'Xing Li Jun, SLC COM TD-SCDMA \(BJ\)'" <lijun.xing@siemens.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: Tue, 18 Jan 2005 12:21:00 -0000 [thread overview]
Message-ID: <NUTMEGsn2Yf0scL9NtD000011cf@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <AF8D5638D08F2348ADD61E563A8989C8044E7787@pekw091a>
> -----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
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-01-18 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 8:54 Xing Li Jun, SLC COM TD-SCDMA (BJ)
2005-01-18 12:21 ` Dave Korn [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 1:15 Xing Li Jun, SLC COM TD-SCDMA (BJ)
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=NUTMEGsn2Yf0scL9NtD000011cf@NUTMEG.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=gdb@sources.redhat.com \
--cc=lijun.xing@siemens.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