DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:reply-to
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=yH9MhInM9Fh+EmSm
	YvzGgHBYgEsfYyRBnH6f54UrAuRrbcFhcpA2wkRDiz3t4zD7RSXqK7VodLtW70ZP
	q6j+tHbqi+kGbdb+KwG/ChiAxoWbKYCat5oeeSzHfEVsRUOkE0j6CuejUnzMUX+u
	eUz64/UcKlvUQt0VQtIxFypBmjM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: tprince AT computer DOT org
Subject: Re: Strange errors running gcc tests on Cygwin
References: <8fa02a72-e684-2ead-eacb-a5347d7594ae AT pobox DOT com>
To: cygwin AT cygwin DOT com
From: "Tim Prince via cygwin" <cygwin AT cygwin DOT com>
Reply-To: Tim Prince <n8tm AT aol DOT com>
Message-ID: <6518f12d-500d-587c-9249-9cd430d929ba@aol.com>
Date: Sat, 4 Mar 2017 06:24:01 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8fa02a72-e684-2ead-eacb-a5347d7594ae@pobox.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


On 3/4/2017 12:48 AM, Daniel Santos wrote:
> Hello. I'm trying to validate a gcc patchset that affects msabi
> functions, so I need good test results on Cygwin, but my unpatched
> tests are getting hundreds of failures for which I cannot determine
> the cause. I'm running Cygwin 64 bit on Windows 7 in a qemu vm (with
> kvm).  My sources are on a C: drive (gcc's HEAD a from a few days
> ago), but I didn't make that device large enough, so I had to add a
> second device on D for the builds.  I have cygdrive set to /  (in
> /etc/fstab, I have "none            /       cygdrive
> binary,posix=0,user 0 0"), but the file names it's printing is using
> the D: format instead of /d.  Example:
>
> FAIL: gfortran.dg/coarray/sync_3.f90 -fcoarray=single  -O2   output
> pattern test, is
> D:/builds/head-test-unpatched-x86_64-pc-cygwin/gcc/testsuite/gfortran2/sync_3.exe:
> error while loading shared libraries: cyggfortran-4.dll: cannot open
> shared object file: No such file or directory
>
> That might not actually be the problem. I do NOT have fortran
> installed.  I have run a successful "make bootstrap" so the build tree
> should have the correct Fortran libs.  The file "cyggfortran-4.dll"
> does exist at the location
> /d/builds/head-test-unpatched-x86_64-pc-cygwin/x86_64-pc-cygwin/libgfortran/.libs/cyggfortran-4.dll.
> The even stranger part is that these errors aren't in the build from
> my patched sources.  Maybe something changed in my environment?  I ran
> my patched tests firsts, which resulted in much fewer failures and I
> haven't re-run them yet to see if it's failing now or not. Any ideas?
> ....
> Also, this is how I have configured gcc:
>
> /c/Users/daniel/proj/sys/gcc/work0/configure --host=x86_64-pc-cygwin
> --build=x86_64-pc-cygwin --target=x86_64-pc-cygwin
> --prefix=/home/daniel/local/gcc-head-test-unpatched-x86_64-pc-cygwin
> --enable-stage1-checking=yes,rtl --enable-lto --enable-gold=yes
> --enable-bootstrap --with-system-zlib
>
>
In order to test gfortran 7.1 without installing, you will need to copy
cyggfortran-4.dll into a folder which is on LD_LIBRARY_PATH.  make check
uses only the dll paths associated with the active gcc (presumably your
bootstrap compiler).  Why not compare your configure and test results
against gcc test results posts?

-- 
Tim Prince


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