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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 30 Dec 2001 14:37:23 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: duplicate regexec/regcomp functions detected Message-ID: <20011230193723.GA13355@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20011228174956 DOT GA30625 AT redhat DOT com> <003201c1909e$0cef0cb0$0e6307d5 AT BRAMSCHE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003201c1909e$0cef0cb0$0e6307d5@BRAMSCHE> User-Agent: Mutt/1.3.23.1i On Sat, Dec 29, 2001 at 08:21:43PM +0100, Ralf Habacker wrote: >Ralf Habacker wrote >>The patch for creating libpthread.a is appended. It contains a script names "speclib" and an >additional rule >in the src/winsup/cygwin/Makefile.in. > >I have recognized yet a little problem with the speclib script. I have checked this from the >cygwin build dir without any errors. If someone was in the winsup dir and does a make cygwin >or make, than some command in speclib does not found the input files. The problem is that ar >does not have an -o option for an output dir, so the hack to emulate that does not work. >Perhaps it is better to use the absolute path of the input library, but currently I have no >idea, how to solve this. :-( >Perhaps anyone else have an idea ? > >speclib > >... >cd $tmpdir >$ar x $PWD/$inlib $FILES >cd .. >... I don't know if this helps bug can I suggest an alternate approach? Use cygwin.din to derive your list of files and do something like: $(LIBPTHREAD_A): speclib new-$(DLL_NAME) cygwin.din pthread.o thread.o /bin/sh ${word 1,$^} $@ "$(NM)" "$(AR)" "$(RANLIB)" ${wordlist 3, 99, $^} cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/