public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Morten Liebach" <m@mongers.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Artifacts in g++ from compilation.
Date: Thu, 24 Oct 2002 08:08:22 +0200	[thread overview]
Message-ID: <20021024060822.GB13301@mongers.org> (raw)

Hi

I'm playing around with somme C++ programming and starts running a
program in ddd and see lines like this one:

std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*) (__out=@0x810f3e0, __s=0x80e3008 "Program: ") at
/var/tmp/portage/gcc-3.2-r1/work/build/i686-pc-linux-gnu/libstdc++-v3/include/bits/ostream.tcc:624
    in /var/tmp/portage/gcc-3.2-r1/work/build/i686-pc-linux-gnu/libstdc++-v3/include/bits/ostream.tcc

and

/var/tmp/portage/gcc-3.2-r1/work/build/i686-pc-linux-gnu/libstdc++-v3/include/ostream: No such file or directory

gdb clearly expects stdlib source files to be present there, but they're
not.

All the references to /var/tmp/portage/gcc-3.2-r1/work/build/<something>
paths makes me worried, shouldn't they point to /usr/include/<something>?

It's on Gentoo Linux 1.4.

% uname -ap
Linux udat.port4.gj1-ds.adsl.cybercity.dk 2.4.19-gentoo-r9 #5 Thu Oct 24 04:07:42 CEST 2002 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
% gcc --version
gcc (GCC) 3.2
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


Have a nice day
                                 Morten

-- 
OpenPGP: 0xF1360CA9 -- 8CF5 32EE A5EC 36B2 4E3F  ACDF 6D86 BEB3 F136 0CA9
         Morten Liebach <m@mongers.org> -- http://m.mongers.org/


                 reply	other threads:[~2002-10-24  6:13 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=20021024060822.GB13301@mongers.org \
    --to=m@mongers.org \
    --cc=gentoo-dev@gentoo.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