From: Daniel Jacobowitz <drow@mvista.com>
To: Klaus Zeitler <kzeitler@lucent.com>
Cc: gdb@sources.redhat.com
Subject: Re: problems building CVS snapshot
Date: Tue, 27 May 2003 14:22:00 -0000 [thread overview]
Message-ID: <20030527142251.GA10062@nevyn.them.org> (raw)
In-Reply-To: <q5gbrxobvho.fsf@lucent.com>
On Tue, May 27, 2003 at 11:16:03AM +0200, Klaus Zeitler wrote:
>
> since I have I few problems with gdb 5.0 and 5.2 under SunOS-5.8 I thought
> I'll go and check the CVS version, thus I fetched gdb+dejagnu-20030526
> and tried configure and make. Here are 4 problems I ran into:
>
> 1. configure complains about sys/ptem.h
>
> checking sys/ptem.h usability... no
> checking sys/ptem.h presence... yes
> configure: WARNING: sys/ptem.h: present but cannot be compiled
> configure: WARNING: sys/ptem.h: check for missing prerequisite headers?
> configure: WARNING: sys/ptem.h: proceeding with the preprocessor's result
> configure: WARNING: ## ------------------------------------ ##
> configure: WARNING: ## Report this to bug-autoconf@gnu.org. ##
> configure: WARNING: ## ------------------------------------ ##
>
> a test C program that additionally contains sys/streams.h does compile.
>
> I reported this yesterday to bug-autoconf and got the following reply:
Thanks for the report. I'll hold on to this, since we are going to be
transitioning to autoconf 2.5x at some point, but this is actually a
problem with your setup. We only support autoconf 2.13.
Try touching all the configure scripts before building so that they are
not rebuilt with your system version of autoconf.
> 2. compile of infrun.c fails
>
> gcc -c -g -O2 -I/usr/include/v9 -I. -I. -I./config -DLOCALEDIR="\"/vol/freeware/SunOS-5.8/gdb+dejagnu/20030526/share/locale\"" -DHAVE_CONFIG_H -I./../include/opcode -I./../readline/.. -I../bfd -I./../bfd -I./../include -I../intl -I./../intl -DMI_OUT=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized infrun.c
> /usr/ccs/bin/as: "/var/tmp/ccWcVZ58.s", line 3774: error: constant value must be between -4096 and 4095
> make[1]: *** [infrun.o] Error 1
> make[1]: Leaving directory `/vol/freeware/source/gdb+dejagnu-20030526/gdb'
This is a bug in GCC. May want to report it to them. I think it's
been fixed or discussed recently.
> 3. normally I don't build in the source directory, but if I try to build
> in a separate build directory, make stops in example/calc with:
>
> configuring in example/calc
> running /bin/sh /vol/freeware/source/gdb+dejagnu-20030526/dejagnu/example/calc/configure --build=sparc-sun-solaris2.8 --host=sparc-sun-solaris2.8 --target=sparc-sun-solaris2.8 --prefix=/vol/freeware/SunOS-5.8/gdb+dejagnu/20030526 --cache-file=../../.././config.cache --srcdir=/vol/freeware/source/gdb+dejagnu-20030526/dejagnu/example/calc
> loading cache ../../.././config.cache
> checking for a BSD compatible install... /bin/sh $s/install-sh -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... (cached) yes
> configure: error: source directory already configured; run make distclean there first
> configure: error: /vol/freeware/source/gdb+dejagnu-20030526/dejagnu/example/calc/configure failed for example/calc
> make: *** [configure-dejagnu] Error 1
> ERROR: gdb: make
This is a known problem in the included dejagnu :(
> 4. on our system is tcl/tk 8.0.5 installed (old I know)
> It seems as if gdb comes with its own tcl (8.4.1) but no tk.
> configure doesn't find the installed tk version (on my system tcl/tk is
> installed under /usr/local/gnu). configure has an option with-tkconfig that
> I could use, but I guess using tcl 8.4.1 together with tk 8.0.5 might be
> asking for trouble anyway.
Can't help you there. I avoid both TCL and Tk whenever possible.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-27 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 9:16 Klaus Zeitler
2003-05-27 14:22 ` Daniel Jacobowitz [this message]
2003-05-28 13:50 ` Klaus Zeitler
2003-05-28 14:19 ` Daniel Jacobowitz
2003-06-06 8:44 ` Klaus Zeitler
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=20030527142251.GA10062@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kzeitler@lucent.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