public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@suse.de>
To: Gerald Pfeifer <gp@suse.de>
Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org, Andreas Jaeger <aj@suse.de>
Subject: Re: pthread related breakage (mainline)
Date: Mon, 08 Dec 2003 13:02:00 -0000	[thread overview]
Message-ID: <3FD47580.6030702@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0312081344510.31896@D209.suse.de>

Gerald Pfeifer wrote:

>On Mon, 8 Dec 2003, Paolo Carlini wrote:
>  
>
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13330
>>>(and then there's also the problem on FreeBSD, that only appears when
>>>using the compiler).
>>>      
>>>
>>Is anyone able to estimate *when* the breakage started?
>>    
>>
>In the last 72 hours, I believe...
>  
>
I see.

Still, absolutely no changes in the libstdc++-v3 directory and many 
toplevel build changes, that I think should be carefully scrutinized: 
the "configury people" are doing a lot of work to move everywhere to 
autoconf 2.57.

Paolo.

  reply	other threads:[~2003-12-08 12:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 10:20 Gerald Pfeifer
2003-12-08 10:34 ` Eric Christopher
2003-12-08 12:12   ` Gerald Pfeifer
2003-12-08 12:47     ` Paolo Carlini
2003-12-08 12:57       ` Gerald Pfeifer
2003-12-08 13:02         ` Paolo Carlini [this message]
2003-12-08 13:16           ` Giovanni Bajo
2003-12-08 13:25             ` Paolo Carlini
2003-12-08 14:43               ` Giovanni Bajo
2003-12-08 23:15             ` Jason Merrill
2003-12-08 23:17               ` Jason Merrill
2003-12-09  4:05                 ` Giovanni Bajo
2003-12-09  5:08                   ` Jason Merrill
2003-12-09 19:09                     ` Giovanni Bajo
2003-12-09 20:11                       ` Jason Merrill
2003-12-08 23:31               ` Paolo Carlini
2003-12-09  1:48                 ` Gabriel Dos Reis
2003-12-08 18:24 Giovanni Bajo
2003-12-08 18:24 ` Paolo Carlini
2003-12-08 18:48   ` Paolo Carlini
2003-12-08 18:59     ` Paolo Carlini
2003-12-08 19:25       ` Janis Johnson

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=3FD47580.6030702@suse.de \
    --to=pcarlini@suse.de \
    --cc=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=gp@suse.de \
    --cc=libstdc++@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).