From: "David Arthur" <darthur@tantacomm.com>
To: "'Eljay Love-Jensen'" <eljay@adobe.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: STL problems in GCC 4.1.2
Date: Thu, 21 Feb 2008 19:27:00 -0000 [thread overview]
Message-ID: <000101c874bf$b67007b0$500010ac@gx520> (raw)
In-Reply-To: <C3E329D4.1C1C%eljay@adobe.com>
Hi Eljay,
"c++ --version" gives the following:
c++ (GCC) 4.1.2 20070115 (prerelease) (SUSE Linux)
Copyright (C) 2006 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.
The "c++ -v --help 2>&1 > cmd.out" results in:
Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2
--enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --program-suffix=
--enable-version-specific-runtime-libs --without-system-libunwind
--with-cpu=generic --host=i586-suse-linux
Thread model: posix
gcc version 4.1.2 20070115 (prerelease) (SUSE Linux)
/usr/lib/gcc/i586-suse-linux/4.1.2/cc1 -quiet -v help-dummy -quiet
-dumpbase help-dummy -mtune=generic -auxbase help-dummy -version --help -o
/tmp/ccaeWc0t.s
/usr/lib/gcc/i586-suse-linux/4.1.2/../../../../i586-suse-linux/bin/as -V
-Qy --help -o /tmp/cc29hxFQ.o /tmp/ccaeWc0t.s
GNU assembler version 2.16.91.0.5 (i586-suse-linux) using BFD version
2.16.91.0.5 20051219 (SUSE Linux)
/usr/lib/gcc/i586-suse-linux/4.1.2/collect2 --eh-frame-hdr -m elf_i386
-dynamic-linker /lib/ld-linux.so.2 --help
/usr/lib/gcc/i586-suse-linux/4.1.2/../../../crt1.o
/usr/lib/gcc/i586-suse-linux/4.1.2/../../../crti.o
/usr/lib/gcc/i586-suse-linux/4.1.2/crtbegin.o
-L/usr/lib/gcc/i586-suse-linux/4.1.2 -L/usr/lib/gcc/i586-suse-linux/4.1.2
-L/usr/lib/gcc/i586-suse-linux/4.1.2/../../../../i586-suse-linux/lib
-L/usr/lib/gcc/i586-suse-linux/4.1.2/../../.. /tmp/cc29hxFQ.o -lgcc
--as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s
--no-as-needed /usr/lib/gcc/i586-suse-linux/4.1.2/crtend.o
/usr/lib/gcc/i586-suse-linux/4.1.2/../../../crtn.o
(I included the "> cmd.out" as the help spews a long output of all options
that are language independent into a file then.)
Any ideas?
Thanks for your help!
Dave
-----Original Message-----
From: Eljay Love-Jensen [mailto:eljay@adobe.com]
Sent: Thursday, February 21, 2008 1:15 PM
To: David Arthur
Subject: Re: STL problems in GCC 4.1.2
Hi David,
What does this command produce:
c++ --version
What does this command produce:
c++ -v --help 2>&1
Sincerely,
--Eljay
next prev parent reply other threads:[~2008-02-21 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 22:11 David Arthur
2008-02-12 22:23 ` Tom Browder
2008-02-12 22:46 ` David Arthur
2008-02-12 23:20 ` James Tebneff
2008-02-14 22:23 ` David Arthur
2008-02-21 18:14 ` David Arthur
[not found] ` <C3E329D4.1C1C%eljay@adobe.com>
2008-02-21 19:27 ` David Arthur [this message]
2008-02-21 19:43 ` Eljay Love-Jensen
2008-02-21 20:08 ` David Arthur
2008-02-21 20:17 ` Eljay Love-Jensen
2008-02-21 22:59 ` Tom Browder
2008-02-22 9:08 ` Tom Browder
2008-02-21 22:59 ` Tom Browder
2008-02-25 14:53 ` Philipp Thomas
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='000101c874bf$b67007b0$500010ac@gx520' \
--to=darthur@tantacomm.com \
--cc=eljay@adobe.com \
--cc=gcc-help@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).