From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 52135 invoked by alias); 4 Mar 2017 11:27:58 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 52121 invoked by uid 89); 4 Mar 2017 11:27:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_MXURI,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 spammy=H*F:D*aol.com, 7.1, posts, H*RU:sk:omr-m00 X-HELO: omr-m009e.mx.aol.com Received: from omr-m009e.mx.aol.com (HELO omr-m009e.mx.aol.com) (204.29.186.8) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 04 Mar 2017 11:27:56 +0000 Received: from mtaout-mab01.mx.aol.com (mtaout-mab01.mx.aol.com [172.26.249.81]) by omr-m009e.mx.aol.com (Outbound Mail Relay) with ESMTP id D41693800081 for ; Sat, 4 Mar 2017 06:27:54 -0500 (EST) Received: from [192.168.200.215] (unknown [72.49.129.109]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-mab01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 9E65238000082 for ; Sat, 4 Mar 2017 06:27:54 -0500 (EST) Reply-To: tprince@computer.org Subject: Re: Strange errors running gcc tests on Cygwin References: <8fa02a72-e684-2ead-eacb-a5347d7594ae@pobox.com> To: cygwin@cygwin.com From: "Tim Prince via cygwin" Reply-To: Tim Prince Message-ID: <6518f12d-500d-587c-9249-9cd430d929ba@aol.com> Date: Sat, 04 Mar 2017 11:27:00 -0000 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 x-aol-global-disposition: G x-aol-sid: 3039ac1af95158baa4ba0579 X-AOL-IP: 72.49.129.109 X-SW-Source: 2017-03/txt/msg00055.txt.bz2 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