From: John Dallaway <john@dallaway.org.uk>
To: Uwe Kindler <uwe.kindler@cetoni.de>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: uSTL config.h clash
Date: Fri, 28 Aug 2009 16:33:00 -0000 [thread overview]
Message-ID: <4A9806C7.30008@dallaway.org.uk> (raw)
Hi Uwe
There's a problem with uSTL's config.h clashing with a header file used
by the SNMP library package. In this case, it is clear that the uSTL
header files should not be polluting the top-level include/ directory
unless this is necessary as part of the contract with application code.
I note that the upstream version of "ustl.h" looks for the other headers
in a ustl/ subdirectory. Are you able to move all the other headers
(including config.h) into include/ustl/ within the package without
disrupting the rest of the sources too much?
John Dallaway
next reply other threads:[~2009-08-28 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 16:33 John Dallaway [this message]
2009-08-29 16:58 Uwe Kindler
2009-08-29 19:43 ` John Dallaway
2009-08-29 20:26 ` John Dallaway
2009-08-29 21:25 ` Uwe Kindler
2009-08-29 21:30 ` Uwe Kindler
2009-08-30 17:39 ` John Dallaway
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=4A9806C7.30008@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-devel@ecos.sourceware.org \
--cc=uwe.kindler@cetoni.de \
/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).