public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
* Re: SID compilation FAIL on alphaev56
       [not found] <3DD2A669.87669C32@iol.unh.edu>
@ 2002-11-13 11:59 ` Ben Elliston
  2002-11-13 12:21   ` bemis
  2002-11-13 12:44 ` Frank Ch. Eigler
  1 sibling, 1 reply; 4+ messages in thread
From: Ben Elliston @ 2002-11-13 11:59 UTC (permalink / raw)
  Cc: sid

The following message is a courtesy copy of an article
that has been posted to gmane.comp.gdb.devel as well.

>>>>> "bemis" == bemis  <bemis@iol.unh.edu> writes:

  bemis> Is anyone currently working on sid?  SID is causing our
  bemis> toolchain build to fail.  I've read about this happening on
  bemis> systems other than alpha in the past.  Is their a know patch
  bemis> for this?

There were some C++ compliance patches committed this week.  You could
try getting a fresh update to see if the problems go away.

Ben

PS: You should post messages about SID to sid@sources.redhat.com.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: SID compilation FAIL on alphaev56
  2002-11-13 11:59 ` SID compilation FAIL on alphaev56 Ben Elliston
@ 2002-11-13 12:21   ` bemis
  2002-11-13 23:05     ` Ben Elliston
  0 siblings, 1 reply; 4+ messages in thread
From: bemis @ 2002-11-13 12:21 UTC (permalink / raw)
  To: Ben Elliston; +Cc: sid

I did post this to the sid mailing list, but All I got a few days later
was a sid cvs  snapshot.
Our sid package has a cvs snapshot of 2002-10-28.  I'll check if there is
a later version.
thanks
-matt bemis



Ben Elliston wrote:

> The following message is a courtesy copy of an article
> that has been posted to gmane.comp.gdb.devel as well.
>
> >>>>> "bemis" == bemis  <bemis@iol.unh.edu> writes:
>
>   bemis> Is anyone currently working on sid?  SID is causing our
>   bemis> toolchain build to fail.  I've read about this happening on
>   bemis> systems other than alpha in the past.  Is their a know patch
>   bemis> for this?
>
> There were some C++ compliance patches committed this week.  You could
> try getting a fresh update to see if the problems go away.
>
> Ben
>
> PS: You should post messages about SID to sid@sources.redhat.com.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: SID compilation FAIL on alphaev56
       [not found] <3DD2A669.87669C32@iol.unh.edu>
  2002-11-13 11:59 ` SID compilation FAIL on alphaev56 Ben Elliston
@ 2002-11-13 12:44 ` Frank Ch. Eigler
  1 sibling, 0 replies; 4+ messages in thread
From: Frank Ch. Eigler @ 2002-11-13 12:44 UTC (permalink / raw)
  To: bemis; +Cc: gdb, sid, clp


bemis <bemis@iol.unh.edu> writes:

> Is anyone currently working on sid?  SID is causing our toolchain
> build to fail. [...]

What toolchain is this?  Do you need sid for this target?  If not, why
is sid in your source tree at all?  If so, we should continue
discussing this on sid@sources.redhat.com; there is no need to bother
gdb people.

- FChE

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: SID compilation FAIL on alphaev56
  2002-11-13 12:21   ` bemis
@ 2002-11-13 23:05     ` Ben Elliston
  0 siblings, 0 replies; 4+ messages in thread
From: Ben Elliston @ 2002-11-13 23:05 UTC (permalink / raw)
  To: bemis; +Cc: sid

>>>>> "bemis" == bemis  <bemis@iol.unh.edu> writes:

  bemis> I did post this to the sid mailing list, but All I got a few
  bemis> days later was a sid cvs snapshot.  Our sid package has a cvs
  bemis> snapshot of 2002-10-28.  I'll check if there is a later
  bemis> version.

I'm sure there will be.  Alternatively, you can check it straight out
of CVS to be sure you've got the latest version.

Cheers, Ben

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-11-14  7:05 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <3DD2A669.87669C32@iol.unh.edu>
2002-11-13 11:59 ` SID compilation FAIL on alphaev56 Ben Elliston
2002-11-13 12:21   ` bemis
2002-11-13 23:05     ` Ben Elliston
2002-11-13 12:44 ` Frank Ch. Eigler

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).