From: "Ken Yee" <kenkyee@excite.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] fstream support conflicts w/ networking package
Date: Mon, 24 Sep 2012 16:15:00 -0000 [thread overview]
Message-ID: <20120924121508.1419@web002.roc2.bluetie.com> (raw)
Forgot to post about this problem/workaround that I hit a while back.
If you see an error like this:
.../ecos_install/include/ustl/config.h:96:52: error: declaration of C function ‘int ioctl(int, CYG_ADDRWORD, ...)’ conflicts with
.../ecos_install/include/sys/ioctl.h:86:5: error: previous declaration ‘int ioctl(int, long unsigned int, ...)’ here
It's because the fstream package conflicts w/ the networking package.
I tried doing all sorts of #undefs and #defines to try to work around it w/ no luck, so I ended up just removing the fstream package which luckily wasn't needed and is a bit of a memory hog anyways...
Now at least the ecos mailing list search engine will find it if anyone else hits it :-)
ken
--
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:[~2012-09-24 16:15 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=20120924121508.1419@web002.roc2.bluetie.com \
--to=kenkyee@excite.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).