Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 22 Aug 2003 12:39:23 -0400
From: Christopher Faylor <cgf-idd AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: It's a snapshot
Message-ID: <20030822163923.GA30603@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <002201c368af$c8fa05a0$6fc82486 AT medschool DOT dundee DOT ac DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002201c368af$c8fa05a0$6fc82486@medschool.dundee.ac.uk>
User-Agent: Mutt/1.4.1i

On Fri, Aug 22, 2003 at 02:17:49PM +0100, fergus AT bonhard DOT uklinux DOT net wrote:
>History: Up to now, and for months past, running everything [curr] on W98/SE
>has been completely bomb-proof apart from occasional problems when running
>XWin and after exiting XWin. (Problems= blue screen; copies of rxvt, bash
>and winoldap left lying around; wget almost always grinding to a halt when
>only part-way through wget'ing stuff.)
>
>What I did next: click on [exp] and install *everything* that was offered.
>
>Now: a few problems.
>
>(1) When attempting to recompile one of only 3 non_cygwin executables that I
>frequently use (and that has been trouble-free both in compilation and
>execution) I got
>
>    /usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/ld:
>final link failed:
>    File truncated
>    collect2: ld returned 1 exit status

This is a specific problem that was supposed to be fixed in the snapshot.
Are you *sure* you're running the snapshot and not 1.5.2?

>(2) Some scripts that are commonly used (by me, I mean) call files from
>elsewhere in the system. Occasionally it has proved necessary to refer to
>their location explicitly as c:/Cygwin/{path to filename} (yes, forward
>slashes) rather than simply {path to filename}. Now I am getting "cannot
>open" error messages at the point that the files are sought. Maybe this is
>as a consequence of some re-vamp (= improvement, in fact) in background
>logic, temporarily denied to me because the executable has not been
>re-compiled, but anyway this is the consequence presently.
>
>(3) Using xdvi, I got simply
>
>    > xdvi a4.dvi
>    Signal 11
>
>That's all I can report at the moment, and I am sorry for these bald
>statements rather than any diagnostic suggestions.

The standard diagnostic suggestion from this direction is to include
cygcheck output.  Could you send that as an attachment, please?

cgf

--
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/