From: Tad <ecos_removethispart@ds3switch.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] ecosconfig CYGPKG_LIBC_STDIO needs CYGFUN_LIBC_STDIO_ungetc?
Date: Tue, 12 Jun 2007 22:51:00 -0000 [thread overview]
Message-ID: <466F116B.8070205@ds3switch.com> (raw)
Perhaps
cdl_package CYGPKG_LIBC_STDIO should have CYGFUN_LIBC_STDIO_ungetc added
to its "requires"
build fails without ungetc:
vsscanf requires vfscanf requries ungetsc
already considered but not included for some reason in stdio.cdl it seems...
requires CYGINT_ISO_STRING_STRFUNCS
96 requires CYGINT_ISO_STRING_MEMFUNCS
97 # The following is for scanf only. We could express this better,
98 # particularly since scanf is also dependent on the optional ungetc.
99 requires CYGINT_ISO_STDLIB_STRCONV
100
101 compile common/fflush.cxx common/feof.cxx \
102 common/freopen.cxx common/setvbuf.cxx \
103 common/snprintf.cxx common/sprintf.cxx \
104 common/sscanf.cxx common/stderr.cxx \
105 common/stdin.cxx common/stdiofiles.cxx \
106 common/fseek.cxx common/stdioinlines.cxx\
107 common/stdiosupp.cxx common/stdout.cxx \
108 common/stream.cxx common/streambuf.cxx \
109 common/ungetc.cxx common/vsnprintf.cxx \
110 common/vsscanf.cxx common/fileops.cxx \
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2007-06-12 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=466F116B.8070205@ds3switch.com \
--to=ecos_removethispart@ds3switch.com \
--cc=ecos-discuss@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).