Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 30 Aug 2004 10:14:42 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: BUG gcc-mingw 20040810-1 library search path In-Reply-To: <1524918411.20040830073143@familiehaase.de> Message-ID: References: <14810259248 DOT 20040829195031 AT familiehaase DOT de> <20040829212630 DOT 32357 DOT qmail AT web40414 DOT mail DOT yahoo DOT com> <1008963871 DOT 20040830011922 AT familiehaase DOT de> <1524918411 DOT 20040830073143 AT familiehaase DOT de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Mon, 30 Aug 2004, Gerrit P. Haase wrote: > Hallo Igor, > > Am Montag, 30. August 2004 um 04:23 schriebst du: > > > On Mon, 30 Aug 2004, Gerrit P. Haase wrote: > >> This is in binutils/ld/configure.tgt: > >> i[3-7]86-*-cygwin*) targ_emul=i386pe ; > >> targ_extra_ofiles="deffilep.o pe-dll.o" > >> test "$targ" != "$host" && > >> LIB_PATH='${tooldir}/lib/w32api' ;; > >> > >> where tooldir should be /usr/i686-pc-mingw32 in this case and you need > >> to have the symlinks installed in /usr/i686-pc-mingw32: > >> 21 Nov 1 2003 bin -> ../i686-pc-cygwin/bin > >> 16 Nov 1 2003 include -> ../include/mingw > >> 12 Nov 1 2003 lib -> ../lib/mingw > >> > >> Now, the library path automatically searched by the linker is: > >> /usr/i686-pc-mingw32/../lib/mingw/w32api > > >> % export tooldir=/usr/i686-pc-mingw32 > >> % ls ${tooldir}/lib/w32api > >> ls: /usr/i686-pc-mingw32/lib/w32api: No such file or directory > > > Ahem. Shouldn't this be > > > $ export tooldir=/usr/i686-pc-mingw32 > > $ ls -ld ${tooldir}/../lib/w32api > > drwxrwxr-x+ 2 Administ SYSTEM 0 Jul 30 17:25 > > /usr/i686-pc-mingw32/../lib/w32api/ > > $ > > > (note the "../")? As you can see, works just fine for me. > > Yes of, course, that is my question, was it changed for binutils > recently? Is tooldir=/usr then it works, if tooldir is /usr/$target, > then it is broken now and either the shortcuts needs to be changed or > ld definitions need to be changed (or tooldir def). Not quite true. If tooldir=/usr, then ${tooldir}/../lib/w32api resolves to /lib/w32api. If tooldir=/usr/$target, then ${tooldir}/../lib/w32api resolves to /usr/lib/w32api. As long as the /usr/lib mount is in order, it should work in both cases, no? FWIW, I don't know what (if anything) has changed... I've used "gcc -mno-cygwin" recently with no problems. What exactly needs to be done to reproduce the problem? Igor > >> Maybe the definition of tooldir for binutlis builds has changed? > >> Sorry, but I don't see where I should change the bits in gcc. > > > To the OP: your problem may potentially be that you're missing the > > /usr/lib mount. However, since you didn't follow the Cygwin problem > > reporting guidelines at , and didn't > > attach the output of "cygcheck -svr" to your report, the above is just a > > WAG. > > No, I don't think that he is missing s.th. I can verify that the > reported problem exists, I see this myself, e.g. when building > libwin32, I just wasn't sure if it was my fault or gcc's or if it was > a binutils issue and didn't searched too long. > > Now I want to know what is the reason since it looks like there were > no changes. Christopher, is the tooldir defined during configure for > binutils or is it defined automatically internally by some logic, and > how is it defined for the ld compilation? -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing." -- Dr. Jubal Harshaw -- 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/