public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwgk at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19298] Error compiling Boost.Python test
Date: Thu, 06 Jan 2005 19:52:00 -0000	[thread overview]
Message-ID: <20050106195157.11946.qmail@sourceware.org> (raw)
In-Reply-To: <20050106194835.19298.rwgk@yahoo.com>


------- Additional Comments From rwgk at yahoo dot com  2005-01-06 19:51 -------
Date: Thu, 06 Jan 2005 14:24:06 -0500
From: David Abrahams

Ralf W. Grosse-Kunstleve wrote:
> Hi David,
> 
> To ensure that Boost.Python will work with gcc 4 I've checked out the
> latest gcc cvs today, along with the latest boost cvs. There are lots
> of errors when compiling the Boost.Python tests, but as far as I can
> tell only two types of errors. One is an internal compiler error, i.e.
> there is no question that I have to file a bug report for this one.
> However, I am not sure about the second one. Could you please have a
> look?
> 
>   Raw error message:
>     http://cci.lbl.gov/~rwgk/bugs/gcc_cvs_head_20050106/error_which_is_of_non_
class_type
> 
>   Same but processed with gSTLFilt.pl:
>     http://cci.lbl.gov/~rwgk/bugs/gcc_cvs_head_20050106/error_which_is_of_non_
class_type_stlfilt

That's not much help, is it!?

> If you think it is a gcc 4 problem rather than a boost problem
> I'll file a bug report.

Well, let's see.  I think you can do this analysis yourself, FWIW:

/net/legless/scratch1/rwgk/hot/boost/boost/python/object/make_instance.hpp:63:
error: request for member M-CM-"M-bM-^BM-,M-KM-^\get_class_objectM-CM-"M-bM-^B
M-,M-bM-^DM-" in
M-CM-"M-bM-^BM-,M-KM-^\boost::python::converter::detail::registered_base<const v
olatile
Y&>::convertersM-CM-"M-bM-^BM-,M-bM-^DM-", which is of non-class type M-CM-"M-b
M-^BM-,M-KM-^\const
boost::python::converter::registration&M-CM-"M-bM-^BM-,M-bM-^DM-"

It seems to be claiming that the static

   registration const&

member named "converters" of

  registered_base<Y const volatile&>

Doesn't have class type.  Clearly wrong.  I mean, it's a reference to an
object of class type, but for all purposes other than initialization you
can do the same things with that as you can do with a class instance.

> Thanks!
>         Ralf
> 
> BTW: Do you know what to make of the strange characters (e.g. M-CM-"M-bM-^BM-,
M-bM-^DM-")?

GCC bug?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19298


  parent reply	other threads:[~2005-01-06 19:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 19:48 [Bug c++/19298] New: " rwgk at yahoo dot com
2005-01-06 19:49 ` [Bug c++/19298] " rwgk at yahoo dot com
2005-01-06 19:52 ` rwgk at yahoo dot com [this message]
2005-01-06 19:55 ` pinskia at gcc dot gnu dot org
2005-01-06 20:11 ` [Bug c++/19298] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-06 21:27 ` pinskia at gcc dot gnu dot org
2005-01-06 23:47 ` wanderer at rsu dot ru
2005-01-07  0:54 ` pinskia at gcc dot gnu dot org
2005-01-07  0:56 ` pinskia at gcc dot gnu dot org
2005-01-07 12:57 ` [Bug c++/19298] [4.0 Regression] dependent type (references) and calling a function method nathan at gcc dot gnu dot org
2005-01-07 17:09 ` cvs-commit at gcc dot gnu dot org
2005-01-07 17:09 ` nathan at gcc dot gnu dot org

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=20050106195157.11946.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).