From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org, dan@imi-test.com
Cc: gdb@sources.redhat.com
Subject: Re: cannot subscript something of type <data variable, no debug info>
Date: Tue, 24 Aug 2004 17:54:00 -0000 [thread overview]
Message-ID: <412B80EF.nailIRH13Q2GM@mindspring.com> (raw)
In-Reply-To: <00e001c48a01$014b02b0$0401a8c0@dan>
Well, it's a relief that the more recent version is the version that
doesn't exhibit the buggy behavior. It might be a SuSE gcc packaging
bug, or it might be an installation bug on your side. We'll never know.
> At this point, tho, I might as well just stick with the 3.3.4 update,
> do you agree?? I'm already compiling it anyway...
Try it; see if it works for you.
Make sure to configure with "--prefix=..." so that you can install
it side by side without disturbing your vendor installation.
next prev parent reply other threads:[~2004-08-24 17:54 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)
2004-08-24 17:52 ` Daniel Jacobowitz
[not found] ` <00e001c48a01$014b02b0$0401a8c0@dan>
2004-08-24 17:54 ` Michael Chastain [this message]
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=412B80EF.nailIRH13Q2GM@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=dan@imi-test.com \
--cc=drow@false.org \
--cc=gdb@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