From: Ben Elliston <bje@redhat.com>
To: Klaus Pedersen <klaus.kruse.pedersen@mail.tele.dk>
Cc: sid@sources.redhat.com
Subject: Re: Fix demo application
Date: Thu, 07 Feb 2002 13:59:00 -0000 [thread overview]
Message-ID: <15458.63681.106333.163570@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <3C59DFDA.3090502@mail.tele.dk>
Hi Klaus,
>>>>> "Klaus" == Klaus Pedersen <klaus.kruse.pedersen@mail.tele.dk> writes:
Klaus> There are two unrelated problems. The first problem seem to be general
Klaus> "bit decay", in the configuration files. They refer to both cpu-mapper
Klaus> and mapper which seem to be the same thing.
Thanks for the report. I applied the .conf file changes verbatim.
Klaus> The other problem fixes some namespace issues with gcc-3.1.
I didn't apply these verbatim, as we have a policy of not imprting
entire namespaces where possible. In some cases, I added `using
std::' declarations and in others, I used fully qualified class names.
Nonetheless, the application now compiles using gcc 3.0 (and I presume
3.1). Please let me know if this is not your finding also.
Cheers, Ben
prev parent reply other threads:[~2002-02-07 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 15:13 Klaus Pedersen
2002-01-31 15:15 ` Ben Elliston
2002-02-07 13:59 ` Ben Elliston [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=15458.63681.106333.163570@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=klaus.kruse.pedersen@mail.tele.dk \
--cc=sid@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).