Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Klaus Zeitler <kzeitler@lucent.com>
To: gdb@sources.redhat.com
Subject: Re: gdb 6.0: build on Solaris 5.8 fails for infrun.c
Date: Tue, 02 Dec 2003 07:25:00 -0000	[thread overview]
Message-ID: <q5g4qwjwuj4.fsf@lucent.com> (raw)
In-Reply-To: <q5gvfq81fl3.fsf@lucent.com>

>>>>> "Klaus" == Klaus Zeitler <kzeitler@lucent.com> writes:
    Klaus> 
>>>>> "Andrew" == Andrew Cagney <cagney@gnu.org> writes:
    Andrew> 
    >>> But with gcc 3.0.4 this file compiled fine and I could produce a gdb
    >>> image.  Though there's still a problem in utils. Make stops now with:
    Andrew> 
    Andrew> Fortunatly these utils don't need to be built before you can use
    Andrew> GDB.  Anyway, this is again weird - .LL177 is a gcc symbol - so
    Andrew> I'm again wondering about GCC?
    Klaus> 
    Klaus> oddly enough I can compile/link this file now with the old 2.95.3
    Klaus> again.  I guess it's time to get a recent gcc version and see how
    Klaus> far I'll get then.

I finally managed to get and build gcc 3.3.2. With this gcc version gdb 6.0
builds without any problems now under Solaris 5.8.

Thanks

Klaus

-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             kzeitler@lucent.com  |
 ------------------------------------------
---
/\___/\
                   \_@ @_/
  ---------------oOO-(_)-OOo---------------
 | A day for firm decisions!!!!! Or is it? |
  ----------------ôôô---ôôô----------------
                  \O/   \O/


      reply	other threads:[~2003-12-02  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23  8:14 Klaus Zeitler
2003-10-23 16:16 ` Andrew Cagney
2003-10-24 10:15   ` Klaus Zeitler
2003-10-27 20:30     ` Andrew Cagney
2003-10-29 10:53       ` Klaus Zeitler
2003-12-02  7:25         ` Klaus Zeitler [this message]

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=q5g4qwjwuj4.fsf@lucent.com \
    --to=kzeitler@lucent.com \
    --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