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: Tue, 18 Jan 2005 08:54:00 -0000 [thread overview]
Message-ID: <AF8D5638D08F2348ADD61E563A8989C8044E7787@pekw091a> (raw)
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!
> -----Original Message-----
> From: Xing Li Jun, SLC COM TD-SCDMA (BJ)
> [mailto:lijun.xing@siemens.com]
> Sent: Monday, January 17, 2005 10:26 AM
> To: Dave Korn; 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: Dave Korn [mailto:dave.korn@artimi.com]
> > Sent: Friday, January 14, 2005 8:54 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: gdb-owner On Behalf Of Xing Li Jun, SLC COM TD-SCDMA (BJ)
> > > Sent: 14 January 2005 08:46
> >
> > > I am building gdb 6.3 on solaris, I have installed gmp, mpfr,
> > > texinfo for it. The configure process is ok, no errors in
> > config.log,
> > > bug when I do make, it will give out the following error:
> > >
> > > make: fatal error: don't know how to make target
> 'doc/observer.texi'
> > > ...
> > > make: fatal error: command failed for target 'all-gdb'
> > > then quit.
> >
> > That file should already have been in the source code;
> > where did you get your
> > sources from? CVS, a snapshot, or the released 6.3 tarball?
> > What do you get
> > when you look in the <sourcedir>/gdb/doc? Is it there? Does
> > it have the wrong
> > permissions?
> >
> >
> > cheers,
> > DaveK
> > --
> > Can't think of a witty .sigline today....
> >
>
> I got the sources from the released 6.3 tarball. When I look
> in the <sourcedir>/gdb/doc, observer.texi is there, with
> permission 644.
> Then I changed the permission to 777, but the problem still exists.
> Another symptom I have just noted is that in
> <builddir>/gdb/config.log, there are many errors reported,
> when checking for argz.h, setenv, stpcpy...etc.
> In the config.log under <builddir>, everything is ok. the
> <builddir>/gdb/config.log is generated after make in invoked.
> Do you know what is wrong?
>
next reply other threads:[~2005-01-18 8:54 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) [this message]
2005-01-18 12:21 ` Dave Korn
-- 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=AF8D5638D08F2348ADD61E563A8989C8044E7787@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).