X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4BC0A8C1.5040802@gmail.com> Date: Sat, 10 Apr 2010 17:35:13 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.7.4: Building Xalan-C results in a unusable library References: <4BC0549A DOT 7050201 AT reto-schneider DOT ch> In-Reply-To: <4BC0549A.7050201@reto-schneider.ch> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 10/04/2010 11:36, Reto Schneider wrote: >> make DESTDIR=/.. install (just "make install" would result in a failing "mkdir -p //usr/local/lib" > call) Heh. That's a very common minor bug in automake-based makefiles that has no consequences on Linux, but fails nastily on Windows. The POSIX spec says that "//" at the beginning of a file path can be reserved for special meanings by the system; Linux doesn't take advantage of this leeway, and just treats it as a null path component, but on Cygwin it was the ideal place to add support for windows-style UNC paths. The bug will be because they've written "$(DESTDIR)/$(prefix)" somewhere in a makefile; there shouldn't be a separator, destdir should always have a trailing one when non-empty, and the construct should just be written "$(DESTDIR)$(prefix)". > Now the strange part: > To me it looks as if this file is broken: > > $ ldd /usr/local/lib/cygxalan-c111.dll > ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x77050000) > kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x76b50000) > KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll (0x75050000) > ??? => ??? (0x6dcc0000) > > All the other dll-files (eg. under /usr/bin/ or /usr/local/bin (have a recent boost installed here) > ) do not have this suspicions ???. That's really peculiar. Something may have gone bizarrely wrong during the build. Do you have a log file? If so, upload it to pastebin.org or somewhere like that, post the URL to the list and I'll take a look and see if I can spot anything unusual. cheers, DaveK -- 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