From: Jonathan Larmour <jlarmour@redhat.com>
To: Grant Edwards <grante@visi.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] sprintf/sscanf w/o stdio package?
Date: Wed, 10 Jan 2001 13:01:00 -0000 [thread overview]
Message-ID: <3A5CCDA9.AEB6CCF@redhat.com> (raw)
In-Reply-To: <20010110144652.A22003@visi.com>
Grant Edwards wrote:
>
> On Wed, Jan 10, 2001 at 08:30:17PM +0000, Jonathan Larmour wrote:
>
> > > Everything builds
> > > (and runs) fine, but now I get error messages from ecosconfig
> > > about missing packages required by STDIO.
> >
> > Which ones? It should require the error and strings packages,
> > but those are the only ones of any consequence.
>
> The only one it's complaining about now is
> CYGPKG_IO_SERIAL_HALDIAG. I presume that's only really
> required if printf() is used?
Ah. Yes that is only required if printf is used. This requirement comes
from a libcdl issue: currently there is no way currently to express that if
CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE is set to /dev/ttydiag or /dev/haldiag,
then you need to have those implemented in the I/O package. This came from
some point before when some user tried to do this (use /dev/ttydiag when
CYGPKG_IO_SERIAL_HALDIAG wasn't enabled). Since CYGPKG_IO_SERIAL_HALDIAG is
the default and most common case this requirement was added.
Maybe the requirement should not exist and I should assume that that user's
mistake was a one-off. Opinions?
Certainly you should be able to comment it out in your sources.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine
prev parent reply other threads:[~2001-01-10 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 9:42 Grant Edwards
2001-01-10 12:30 ` Jonathan Larmour
2001-01-10 12:43 ` Grant Edwards
2001-01-10 13:01 ` Jonathan Larmour [this message]
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=3A5CCDA9.AEB6CCF@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.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).