On 22 May 2008, at 18:12, James Mckenzie wrote: > As I reported earlier, it appears that library files are being > created in: > /sw/src/fink.build/root-pwlib-1.10.10/sw/lib/lib > > It appears that make files are also being 'buried' in a duplicate > file structure and are located at: > /sw/src/fink.build/root-pwlib-1.10.10/sw/share/make/make > > At this time, I would respectfully ask that someone with Tiger > (10.4) build this module and see if there are 'duplicate' > directories. This may be a bug with Leopard ONLY and this is to > confirm this. > > The effect of the duplicate directories is that the .deb packager > is erroring and thus the outbound package is not built. This > appears only to happen with pwlib1 as I have built gcc-4.3.2 and > other packages and this error did not occur or was compensated for.
People have built it both on 10.4 and on 10.5 .. You were already told twice that the prime suspect was that you had a non-standard cp 1) the first time in the msg of Martin Costabel on may 20, to cite : > Jean-François Mertens wrote: > [] > > 1) among others there was the question > > 'what does "man cp" tell about the -P flag ? ' > > I was suspicious because of the warnings > > "cp: Warning: the meaning of `-P' will change in the future to > > conform to POSIX. > > Use `--parents' for the old meaning, and `--no-dereference' for the > > new one." > > that I saw in the log-file you had posted there. > > I don't see such a warning coming from Leopard's cp. > And indeed the explanation in "man cp" of the -P flag has not changed: (i.e., does mean `--no-dereference' ) The warnings referred to above are those that your build-log shows after the "cp -pPR" commands in the InstallScript: i.e., your cp iappears to be non-standard (neither Apple's nor the one of coreutils). And indeed your lib/lib and make/make directories are exactly what "cp -pPR" should generate if "-P" was interpreted as "--parents" rather than "--no-dereference" ... 2) On may 21, in absence of reaction from you, I insisted : > You didn't yet tell us even which was your "cp" command, > which acording to Martin's msg above in the thread looks quite > suspicious, > (besides not answering any questions on your own bug-tracker item...) > _ i.e. : > # which cp > # ls -l `which cp` > # dpkg -S `which cp` > > and if relevant, the corresponding output of "fink list -t" ... If you don't answer such questions, how do you want us to help ? Only you can know what's on your system, which cp command is used and where it came from, _ and finally repair your system... JF Mertens ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
