From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: alsa-conf cvscompile fails with 'friend declaration requires class-key'
Date: Sun, 25 Jul 2004 14:57:26 -0400 [thread overview]
Message-ID: <1090781846.14951.42.camel@mindpipe> (raw)
Here is what happens when cvscompile runs make in alsa-conf:
make all-recursive
make[1]: Entering directory `/home/rlrevell/cvs/alsa/alsa-conf'
Making all in newt
make[2]: Entering directory `/home/rlrevell/cvs/alsa/alsa-conf/newt'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/rlrevell/cvs/alsa/alsa-conf/newt'
make[2]: Entering directory `/home/rlrevell/cvs/alsa/alsa-conf'
if g++ -DHAVE_CONFIG_H -I. -I. -I. -I./newt -g -Wall -ftemplate-depth-20 -MT Def.o -MD -MP -MF ".deps/Def.Tpo" \
-c -o Def.o `test -f 'Def.cc' || echo './'`Def.cc; \
then mv -f ".deps/Def.Tpo" ".deps/Def.Po"; \
else rm -f ".deps/Def.Tpo"; exit 1; \
fi
In file included from Value.hh:26,
from Def.hh:27,
from Def.cc:22:
Ptr.hh:181: error: friend declaration requires class-key, i.e. `friend class
CPtr<T>'
In file included from Def.hh:27,
from Def.cc:22:
Value.hh:67: error: parse error before `<' token
Value.hh:70: error: parse error before `&' token
etc.
This is on Debian unstable.
Lee
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
next reply other threads:[~2004-07-25 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 18:57 Lee Revell [this message]
2004-07-27 13:22 ` alsa-conf cvscompile fails with 'friend declaration requires class-key' Takashi Iwai
2004-07-27 16:19 ` Clemens Ladisch
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=1090781846.14951.42.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
/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