peer-io.c: In function ‘tr_evbuffer_write’: peer-io.c:285:31: error: dereferencing pointer to incomplete type make[1]: *** [peer-io.o] Error 1 --- This one REALLY has me curious as to how it was build for the distribution, since I have been unable to build transmission from their source repo for some time due to something along the lines of (if not the exact same) error I'm getting from the 11.4 package. I have a system that seems to be fully updated to 11.4, and installed the appropriate build-requires. Yet another rpmbuild -bb fails with errors indicating it never should have been buildable to a binary in the first place. So what's going on? ---- FWIW, I also tried using the "build" command to see if that worked any better...: expanding package dependencies... reqesting dir:///Share/suse/11.4/repo/oss/suse/x86_64/rpm-4.8.0-27.1.x86_64.rpm failed: 501 Protocol scheme 'dir' is not supported Warning: distribution not specified, assuming 'default' (see /usr/lib/build/configs). downloading zypp://Open_Suse_11.4_Update/rpm/x86_64/Mesa-7.10.2-7.3.1.x86_64.rpm ... reqesting dir:///Share/suse/11.4/update/rpm/x86_64/Mesa-7.10.2-7.3.1.x86_64.rpm failed: 501 Protocol scheme 'dir' is not supported So how does one build binary RPM's from source rpm's or am I just getting 'lucky' in choosing broken SRPM's? :-( (and people want me to use the build-system to build updates for products...um... a main reason for resisting that has been being able to make sure I wasn't building in a 'walled garden', that included things I didn't know about. In it's simplest form, this merely means the build environment seems to include things that aren't obvious to someone building the packages on a standard 11.4 system.... As such, it doesn't seem to be a "portable" build environment... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org