From: Daniel Jacobowitz <drow@mvista.com>
To: Klaus Zeitler <kzeitler@lucent.com>
Cc: gdb@sources.redhat.com
Subject: Re: problems building CVS snapshot
Date: Wed, 28 May 2003 14:19:00 -0000 [thread overview]
Message-ID: <20030528141948.GB906@nevyn.them.org> (raw)
In-Reply-To: <q5gd6i3b2pp.fsf@lucent.com>
On Wed, May 28, 2003 at 03:49:54PM +0200, Klaus Zeitler wrote:
> >>>>> "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
Make sure you rebuilt the affected configures with the older autoconf.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-28 14:19 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
2003-05-28 14:19 ` Daniel Jacobowitz [this message]
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=20030528141948.GB906@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