From: "Daniel Miller \(IMI\)" <dan@imi-test.com>
To: "Michael Chastain" <mec.gnu@mindspring.com>, <drow@false.org>
Cc: <gdb@sources.redhat.com>
Subject: Re: cannot subscript something of type <data variable, no debug info>
Date: Tue, 24 Aug 2004 17:48:00 -0000 [thread overview]
Message-ID: <00e501c48a02$a25b8110$0401a8c0@dan> (raw)
In-Reply-To: <412B78D8.nailIPD1ZS2MK@mindspring.com>
gcc 3.3.4 works properly, both in the tester utility and in our application,
as well as in kdevelop!!
Thank you both for your insightful assistance... I think we can consider
this issue closed...
Dan Miller
----- Original Message -----
From: "Michael Chastain" <mec.gnu@mindspring.com>
To: <drow@false.org>; <dan@imi-test.com>
Cc: <gdb@sources.redhat.com>
Sent: Tuesday, August 24, 2004 10:20
Subject: Re: cannot subscript something of type <data variable, no debug
info>
> Daniel Jacobowitz <drow@false.org> wrote:
> > The two of you should probably compare RPM package versions of the
> > compiler.
>
> Oh! I didn't know that SuSE is RPM-based now!
>
> What have you got, Dan?
>
> % cat /etc/SuSE-release
>
> SUSE LINUX Enterprise Server 9 (i586)
> VERSION = 9
>
> % rpm -q gcc gcc-c++ binutils
>
> gcc-3.3.3-43.24
> gcc-c++-3.3.3-43.24
> binutils-2.15.90.0.1.1-32.5
>
> % rpm -qi gcc gcc-c++ binutils # with editing
>
> Name: gcc-c++
> Version: 3.3.3
> Build Date: Wed 30 Jun 2004 01:21:54 PM EDT
> Source RPM: gcc-3.3.3-43.24.src.rpm
>
> Name: gcc
> Version: 3.3.3
> Build Date: Wed 30 Jun 2004 01:21:54 PM EDT
> Source RPM: gcc-3.3.3-43.24.src.rpm
>
> Name: binutils
> Version: 2.15.90.0.1.1
> Build Date: Wed 30 Jun 2004 12:24:56 PM EDT
> Source RPM: binutils-2.15.90.0.1.1-32.5.src.rpm
>
>
>
next prev parent reply other threads:[~2004-08-24 17:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 1:23 Daniel Miller (IMI)
2004-08-21 2:11 ` Daniel Jacobowitz
2004-08-23 20:49 ` Daniel Miller (IMI)
2004-08-23 21:15 ` Michael Chastain
2004-08-23 21:28 ` Michael Chastain
2004-08-23 22:30 ` Daniel Miller (IMI)
2004-08-24 2:20 ` Michael Chastain
2004-08-24 12:12 ` Michael Chastain
2004-08-24 16:25 ` Daniel Miller (IMI)
2004-08-24 16:34 ` Daniel Jacobowitz
2004-08-24 16:40 ` Daniel Miller (IMI)
2004-08-24 16:54 ` Michael Chastain
2004-08-24 16:32 ` Daniel Miller (IMI)
2004-08-24 16:54 ` Daniel Miller (IMI)
2004-08-24 16:55 ` Daniel Jacobowitz
2004-08-24 17:20 ` Michael Chastain
2004-08-24 17:48 ` Daniel Miller (IMI) [this message]
2004-08-24 17:52 ` Daniel Jacobowitz
[not found] ` <00e001c48a01$014b02b0$0401a8c0@dan>
2004-08-24 17:54 ` Michael Chastain
2004-08-23 20:56 Daniel Miller (IMI)
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='00e501c48a02$a25b8110$0401a8c0@dan' \
--to=dan@imi-test.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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