From: Klaus Zeitler <kzeitler@lucent.com>
To: gdb@sources.redhat.com
Subject: Re: problems building CVS snapshot
Date: Wed, 28 May 2003 13:50:00 -0000 [thread overview]
Message-ID: <q5gd6i3b2pp.fsf@lucent.com> (raw)
In-Reply-To: <20030527142251.GA10062@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>> 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:
Daniel>
Daniel> Thanks for the report. I'll hold on to this, since we are going
Daniel> to be transitioning to autoconf 2.5x at some point, but this is
Daniel> actually a problem with your setup. We only support autoconf 2.13.
I've now installed autoconf 2.13 and get the same message
>> 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'
Daniel>
Daniel> This is a bug in GCC. May want to report it to them. I think it's
Daniel> been fixed or discussed recently.
yes, it seems to be fixed, it compiles with gcc 3.0.4
>> 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.
Daniel>
Daniel> Can't help you there. I avoid both TCL and Tk whenever possible.
wholeheartedly agree :-)
Thanks
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
Nichts auf der Welt ist so gerecht verteilt wie der Verstand. Denn
jedermann ist überzeugt, daà er genug davon habe. -- Rene Descartes
next prev parent reply other threads:[~2003-05-28 13:50 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
2003-05-28 13:50 ` Klaus Zeitler [this message]
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=q5gd6i3b2pp.fsf@lucent.com \
--to=kzeitler@lucent.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