Andreas Jaeger wrote:
Are you using the build command?
All I can say is that it builds without problems. Otherwise you would not have a src rpm to look at ;-)
Andreas
I understand, I think, your point -- how did the src rpm get generated if it didn't work. That's what I'm trying to find out. I'm using rpmbuild -ba. I'm doing things that build might not support -- but that *shouldn't* make a difference. If I find something that is making the difference, I want to understand why its failing and correct the problem. 1) My initial purpose was to drain the swamp that had the alligators in it...no. Wait, that was last week. 1a) Initial purpose was to apply high-performance source patches to scp/ssh. Goal -- going from current ~3MB/s up to about 10 times that. Max raw TCP with jumbo packets was over 90MB/s. So I have a bit of headroom to improve on. Max file transfer with normal size packets was ~70+MB/s over UDB (CIFS). I hoped NFS/TCP would do better, but that hasn't been the case so far. Nevertheless, my most common method of xferring files has been scp/ssh. So that's my short-term goal. The patches were available against 4.7 or 5.0 versions of openssh. suse10.3 has 4.6 in it. I thought I'd have better luck in 'eventual integration into my systems if I started with a suSE rpm -- I prefer packaging my software mods in rpms -- they are usually fairly stable ways of reproducing the software and preserving its source for later. I checked suse11.0 -- and it is using openssh5.0 -- one of the versions supported by the patchsets. Discovered via trial&error that applying the high-perf patches, Then applying the rest of the suse patches generated fewest conflicts. Only conflict was in a makefile that added suse's libaudit to a link. So at this point, I'm building across releases 11.0 src rpm on 10.3 with 3rd party patches. Is this something "build" is designed for? I had one incompatibility in the resulting 11.0 binary that wanted a krb-gssapi routine I wasn't familiar with. I just assumed it might be new in 11.0 -- and I needed it, I'd need to regen those libs, *however* I don't need krb-gssapi, and since that's an optional component when specifying open-ssh's "Configure" options, I removed it. Now is when I ran into the missing pthread problem. It happens in building a 'subutil' built within the openssh rpm. The openssh.spec builds 2 or 3 separate components -- most recently 'openssh-askpass' was merged (was separate in 10.3). During the change-over, someone removed the pthreads lib from the global LDFLAGS var. While that works for the main prog and the new askpass util, it caused missing libpthread calls in one subpackage. They actually removed it for the entire package -- and it seems it is only this one subpackage that needs it. There's even a comment in the .spec file that says the "posix threads' defines and -lpthread call were "Obsoleted" -- but no reason saying why. -- So whoever made the change thought they had done something to eliminate the need. Maybe that need is hidden or taken care of by using the build command -- but the downside is that the source rpm no longer can be used to build the rpm stand-alone. Whether or not 'build' could be used to reproduce the issue, I don't know -- it's certainly alot more setup to rebuild the openssh package -- "-ba" takes about a minute. It doesn't appear that build would be quite so fast -- and I'm not sure about it's flexibility -- but if it is hiding problems that are 'valid' problems in standalone rpmbuild commands, that's troubling and like peculiar. 99. So now as I find myself up to my bum in alligators...(so to speak...) -- trying to figure out why the rpmbuild command isn't working when it "should"... Am I making sense about why I'm going about and doing things the way I am? Sorry to stir things up needlessly if things were really fine before...really not sure why it wouldn't work now...just weird. Linda ...very tired...brain only firing on a few cylinders... so will have to see if I can sleep now (have sporadic sleeplessness...so...of course I get on my computer and do relaxing things like this...:-) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org