public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: bemis <bemis@iol.unh.edu>
To: sid@sources.redhat.com, clp <clp@iol.unh.edu>
Subject: c++ error with sid bootstrap-gcc_3.2
Date: Mon, 07 Oct 2002 07:25:00 -0000	[thread overview]
Message-ID: <3DA19953.64A22D82@iol.unh.edu> (raw)

Hello,
I hope someone reads this list.
This error occured on an 686 platform while compiling the toolchain with
bootstrap-gcc_3.2 baseline
Is this problem solved by adding hash to the namespace or a build error
on our part?

/bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I.
-I/home/buildsys/sourc
e/toolchain/sid/component/bochs/vga -I.. -I../../../include
-I/home/buildsys/sou
rce/toolchain/sid/component/bochs/vga
-I/home/buildsys/source/toolchain/sid/comp
onent/bochs/vga/..
-I/home/buildsys/source/toolchain/sid/component/bochs/vga/../
../../include
-I/home/buildsys/source/toolchain/sid/component/bochs/vga/../cpu -
I/home/buildsys/source/toolchain/sid/component/bochs/vga/../../memory
-g -O2
-c
/home/buildsys/source/toolchain/sid/component/bochs/vga/sid-vga-wrapper.cc

c++ -DHAVE_CONFIG_H -I.
-I/home/buildsys/source/toolchain/sid/component/bochs/vg
a -I.. -I../../../include
-I/home/buildsys/source/toolchain/sid/component/bochs/
vga -I/home/buildsys/source/toolchain/sid/component/bochs/vga/..
-I/home/buildsy
s/source/toolchain/sid/component/bochs/vga/../../../include
-I/home/buildsys/sou
rce/toolchain/sid/component/bochs/vga/../cpu
-I/home/buildsys/source/toolchain/s
id/component/bochs/vga/../../memory -g -O2
-Wp,-MD,.deps/sid-vga-wrapper.pp -c /
home/buildsys/source/toolchain/sid/component/bochs/vga/sid-vga-wrapper.cc
-o sid
-vga-wrapper.o
In file included from
/home/buildsys/source/toolchain/sid/component/bochs/vga/si
d-vga-wrapper.h:15,
                 from
/home/buildsys/source/toolchain/sid/component/bochs/vga/si
d-vga-wrapper.cc:7:
/home/buildsys/source/toolchain/sid/include/sidattrutil.h: In member
function
   `size_t sidutil::hash_string::operator()(const std::string&) const':
/home/buildsys/source/toolchain/sid/include/sidattrutil.h:696: `hash'
   undeclared in namespace `std'
/home/buildsys/source/toolchain/sid/include/sidattrutil.h:696: parse
error
   before `;' token

snips from sid/include/sidattrutil.h

689 #ifdef HAVE_HASHING
690   struct hash_string
691   {
692    size_t
693    operator () (const std::string& s) const
694      {
695        // XXX: improve?
696        return std::hash<const char*> () (s.c_str ());
697      }
698   };
699 #endif


the name space looks like this

namespace sidutil
{

  // Make a string from an object by the default output-streaming
operator.
  template <typename Type>
  static std::string
  make_attribute (const Type& value)
  {
#if HAVE_SSTREAM
    std::ostringstream stream;
    stream << value;
    return stream.str ();
#elif HAVE_STRSTREAM_H
    ostrstream stream;
    stream << value;
    std::string result (stream.str (), stream.pcount ());
    stream.freeze (0);
    return result;
#else
#error "need <sstream> or <strstream.h>!"
#endif
  }



                 reply	other threads:[~2002-10-07 14:25 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=3DA19953.64A22D82@iol.unh.edu \
    --to=bemis@iol.unh.edu \
    --cc=clp@iol.unh.edu \
    --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).