X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG X-Spam-Check-By: sourceware.org Message-ID: <4F5FCDD5.4020702@gmail.com> Date: Tue, 13 Mar 2012 23:44:37 +0100 From: marco atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: error while loading shared libraries: ?: cannot open shared object file: No such file or directory References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 3/13/2012 11:10 PM, Ted wrote: > I see this error in 3 different products either so I can use them, or develop > them. > > 1) Atlas - I am trying to build it, with Lapack, to squeeze a little more speed > > out of my number crunching code. But here is precisely what happens: > > Ted AT Ted-acer-i7w7 ~/ATLAS/atlasbuild > $ ../configure -Ss lasrc ../../lapack-3.4.0/SRC -Si latune 1 > gcc -I/cygdrive/c/cygwin//home/Ted/ATLAS/atlasbuild/..//CONFIG/include -g -w -c > > /cygdrive/c/cygwin//home/Ted/ATLAS/atlasbuild/..//CONFIG/src/atlconf_misc.c > gcc -I/cygdrive/c/cygwin//home/Ted/ATLAS/atlasbuild/..//CONFIG/include -g -w -o > > xconfig /cygdrive/c/cygwin//home/Ted/ATLAS/atlasbuild/..//CONFIG/src/config.c > atlconf_misc.o > ./xconfig -d s /cygdrive/c/cygwin//home/Ted/ATLAS/atlasbuild/../ -d b > /cygdrive/c/cygwin//home/Ted/ATLAS/atlasbuild -Ss lasrc ../../lapack-3.4.0/SRC > -Si latune 1 > /home/Ted/ATLAS/atlasbuild/xconfig.exe: error while loading shared libraries: ?: > > cannot open shared object file: No such file or directory > xconfig exited with 127 > > Ted AT Ted-acer-i7w7 ~/ATLAS/atlasbuild > $ cygcheck ./xconfig > C:\cygwin\home\Ted\ATLAS\atlasbuild\xconfig.exe > C:\cygwin\bin\cygwin1.dll > C:\Windows\system32\KERNEL32.dll > C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll > C:\Windows\system32\ntdll.dll > C:\Windows\system32\KERNELBASE.dll > C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll > > Of course I checked, and all the required DLLs exist in he expected locations. > > 2) gsl: I need to use it to do some stats in C++ (and ultimately I want to build > > it to use ATLAS). But the last test fails with the following: > > make[1]: Entering directory `/home/Ted/gsl-1.15/statistics' > make test.exe > make[2]: Entering directory `/home/Ted/gsl-1.15/statistics' > gcc -DHAVE_CONFIG_H -I. -I.. -I.. -g -O2 -MT test.o -MD -MP -MF > .deps/test.Tpo -c -o test.o test.c > mv -f .deps/test.Tpo .deps/test.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I.. -g -O2 -MT test_nist.o -MD -MP -MF > .deps/test_nist.Tpo -c -o test_nist.o test_nist.c > mv -f .deps/test_nist.Tpo .deps/test_nist.Po > /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o test.exe test.o > test_nist.o libgslstatistics.la ../sort/libgslsort.la > ../ieee-utils/libgslieeeutils.la ../err/libgslerr.la ../test/libgsltest.la > ../sys/libgslsys.la ../utils/libutils.la -lm > libtool: link: gcc -g -O2 -o .libs/test.exe test.o test_nist.o > ./.libs/libgslstatistics.a ../sort/.libs/libgslsort.a > ../ieee-utils/.libs/libgslieeeutils.a ../err/.libs/libgslerr.a > ../test/.libs/libgsltest.a .. > /sys/.libs/libgslsys.a ../utils/.libs/libutils.a > /home/Ted/gsl-1.15/statistics/test.exe: error while loading shared libraries: > ?:cannot open shared object file: No such file or directory > make[2]: Leaving directory `/home/Ted/gsl-1.15/statistics' > make check-TESTS > make[2]: Entering directory `/home/Ted/gsl-1.15/statistics' > /home/Ted/gsl-1.15/statistics/test.exe: error while loading shared libraries: > ?:cannot open shared object file: No such file or directory > FAIL: test.exe > ================== > 1 of 1 test failed > ================== > Makefile:436: recipe for target `check-TESTS' failed > make[2]: *** [check-TESTS] Error 1 > make[2]: Leaving directory `/home/Ted/gsl-1.15/statistics' > Makefile:558: recipe for target `check-am' failed > make[1]: *** [check-am] Error 2 > make[1]: Leaving directory `/home/Ted/gsl-1.15/statistics' > Makefile:656: recipe for target `check-recursive' failed > make: *** [check-recursive] Error 1 > > Observe, the line just above "FAIL: test.exe" is the same error that I get with > > ATLAS! Here are he DLLs that test.exe depends on: > > Ted AT Ted-acer-i7w7 ~/gsl-1.15/statistics > $ cygcheck ./test.exe > C:\cygwin\home\Ted\gsl-1.15\statistics\test.exe > C:\cygwin\bin\cygwin1.dll > C:\Windows\system32\KERNEL32.dll > C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll > C:\Windows\system32\ntdll.dll > C:\Windows\system32\KERNELBASE.dll > C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll > > > 3) My own test program (I am trying to familiarize myself with GSL). Here is > > the relevant output: > > Ted AT Ted-acer-i7w7 ~/New.Task/NKs-sd-02-24-12/NKs-sd/tests > $ ./test.gsl > /home/Ted/New.Task/NKs-sd-02-24-12/NKs-sd/tests/test.gsl.exe: error while > > loading shared libraries: ?: cannot open shared object file: No such file or > > directory > > Ted AT Ted-acer-i7w7 ~/New.Task/NKs-sd-02-24-12/NKs-sd/tests > $ cygcheck ./test.gsl.exe > C:\cygwin\home\Ted\New.Task\NKs-sd-02-24-12\NKs-sd\tests\test.gsl.exe > C:\cygwin\bin\cygwin1.dll > C:\Windows\system32\KERNEL32.dll > C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll > C:\Windows\system32\ntdll.dll > C:\Windows\system32\KERNELBASE.dll > C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll > C:\cygwin\bin\cyggsl-0.dll > C:\cygwin\lib\lapack\cygblas-0.dll > C:\cygwin\bin\cyggfortran-3.dll > C:\cygwin\bin\cyggcc_s-1.dll > C:\cygwin\bin\cygstdc++-6.dll > > Ted AT Ted-acer-i7w7 ~/New.Task/NKs-sd-02-24-12/NKs-sd/tests > $ cygcheck ./test.sd.exe > C:\cygwin\home\Ted\New.Task\NKs-sd-02-24-12\NKs-sd\tests\test.sd.exe > C:\cygwin\bin\cygwin1.dll > C:\Windows\system32\KERNEL32.dll > C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll > C:\Windows\system32\ntdll.dll > C:\Windows\system32\KERNELBASE.dll > C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll > C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll > C:\cygwin\bin\cyggcc_s-1.dll > C:\cygwin\bin\cygstdc++-6.dll > > Ted AT Ted-acer-i7w7 ~/New.Task/NKs-sd-02-24-12/NKs-sd/tests > $ > > Now, I am baffled, as I ran the check on test.sd because it had previously > > worked. But now, after I let cugwyn's setup update gcc, it too fails. here > is what GCC now reports itself to be: > > Ted AT Ted-acer-i7w7 ~/New.Task/NKs-sd-02-24-12/NKs-sd/tests > $ gcc -v > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/4.5.3/lto-wrapper.exe > Target: i686-pc-cygwin > > (some configuration detail you undoubtedly know betteer than IThread model: posix > gcc version 4.5.3 (GCC) > > I did notice, during an install of a couple extra libraries, that setup popped > > open a message saying there was a newer version of setup, but I ignored it as > > that ought not break an installatin that had been worked for quite a while; or > > so I expected. > > So, then, how do I fix this? > > Thanks > > Ted > > PS: Your editor complained about lines longer than 80 characters and demanded > I change that before it would post, so please excuse the mangled formatting. > > > you forgot this point: > Problem reports: http://cygwin.com/problems.html we have no clue of wich package versions you are running. Suggestion from my side: - assure to have the latest package versions. Eventually try also one one the last cygwin snapshots as there is additional diagnostic for loading dll. - rebaseall (from dash shell of course) - why you need to compile gsl ? there is already a 1.15-1 package for it. - Atlas is a nasty beast to compile. Looks on the source package I prepared for 3.68 + lapack-3.4.0 http://matzeri.altervista.org/cygwin-1.7/atlas/index.html It should make the effort simpler using cygport to build the package Regards Marco -- 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