> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf > Of Christopher Faylor > Sent: Sunday, December 30, 2001 8:37 PM > To: [EMAIL PROTECTED] > Subject: Re: duplicate regexec/regcomp functions detected > > > 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, $^} > > That means, that libpthread contains all symbols of cygwin.dll and not only the symbols from pthread, which are published in pthread.h ? Does libpthread should only contain pthread relates symbols ?
Ralf -- 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/
