Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Hillel (Sabba) Markowitz" <Sabba.Hillel@verizon.net>
To: Joel Brobecker <brobecker@gnat.com>
Cc: GDB help mailing list <gdb@sources.redhat.com>
Subject: Re: GDB build fails on DEC OSF V5.1a but not OSF V4.0f
Date: Fri, 20 Dec 2002 03:37:00 -0000	[thread overview]
Message-ID: <3E030124.32517705@verizon.net> (raw)
In-Reply-To: <20021220111814.GI1137@gnat.com>

Joel Brobecker wrote:
> 
> > gcc-3.2.1 with a basic hellow world (though any test program works the
> > same
> [...]
> > gdb testit
> 
> Unfortunately, I don't have a gcc-3.2 on our Tru64 machine, so I won't
> be able to help you. I remember that we had a problem with the debugger
> when we built the same sources using our work-in-progress gcc-3.2-based
> version of GNAT, but the symptoms where different.
> 
> (you forgot to tell which version of GDB you were using, BTW. And also
> the commands you used to build it. I assume "configure; make;", but it
> would be nice to confirm it).
> 
> --
> Joel

gdb-5.3 but gdb-5.2.1 and gdb-5.2 had the same symptoms

configure --prefix=/usr/local/GNU --enable-shared --enable-static
--enable-bfd-64-bit as well as a specific set of settings for
tcl-libraries, tcl-includes, tk-libraries and tk-includes

However, I also tested with a basic 

configure --prefix=/usr/local/GNU

as well to make sure that it was not the settings

I used gmake (GNU make) explicitly.

-- 
Said the fox to the fish, "Join me ashore".
The fish are the Jews, Torah is our water.

Hillel (Sabba) Markowitz
sabbahem@bcpl.net, Sabba.Hillel@verizon.net


      reply	other threads:[~2002-12-20 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  9:18 Hillel (Sabba) Markowitz
2002-12-20  2:13 ` Joel Brobecker
2002-12-20  3:07   ` Hillel (Sabba) Markowitz
2002-12-20  3:18     ` Joel Brobecker
2002-12-20  3:37       ` Hillel (Sabba) Markowitz [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=3E030124.32517705@verizon.net \
    --to=sabba.hillel@verizon.net \
    --cc=brobecker@gnat.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