X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_13,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49D9B132.6070601@gmail.com>
Date: Mon, 06 Apr 2009 08:37:22 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [1.7]: For the love of god, don't update!
References: <49D97797 DOT 9080902 AT gmail DOT com> <49D9913B DOT 7030708 AT cwilson DOT fastmail DOT fm> <49D99981 DOT 4030503 AT gmail DOT com> <49D99A02 DOT 7070407 AT gmail DOT com> <49D99D65 DOT 8040304 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <49D99D65.8040304@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Charles Wilson wrote:
> Dave Korn wrote:
> 
>>   Forgot to say... can I see your "cygcheck -cd"?  I would have said "just m4
>> and cygwin", but maybe it's related to something else.
> 
> Attached.  FWIW, I had no problems building other things, like
> yesterday's p7zip packages or today's alternatives packages.

  Grr.  Building binutils with GCC3 doesn't seem to make any difference.
Building Cygwin1.7 with Cygwin1.5 doesn't seem to make any difference.
Building with the released binutils or a more recent version doesn't seem to
make any difference.  Oh, and the debugger doesn't work.  And nothing has any
debugging symbols in it.

  If anyone has any ideas apart from 1) try an older dll 2) try the newest dll
3) try older binutils 4) try newer binutils 5) try debugging it in gdb 6) try
using gcc-3 7) try using gcc-4 8) try building the dll from source or 9) try
building an earlier cvs version of the DLL, I'd dearly like to hear them.  I'm
getting pretty bored of trying variations on those nine ideas though (14 hours
solid of endless rebuilds and absolutely zero sign of anything making the
least bit of difference).

  I'm about to use the time machine to install a completely fresh cygwin in a
vm.  Maybe that'll get things moving again.


    cheers,
      DaveK


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/