https://bugzilla.novell.com/show_bug.cgi?id=176528 ------- Comment #7 from andreas.hanke@gmx-topmail.de 2007-01-08 17:06 MST ------- Why don't you post both your reports and your (so far incorrect) patches ("temporary hacks") upstream, where they belong and where someone with write access to the openssh source can review, fix and commit them? openssh obviously builds fine in the SUSE build system and also elsewhere if the environment is the same as in the SUSE build system. That's why openSUSE ships a tool to build packages in the same environment as the SUSE build system does. I really wonder what will happen if users continue to report build failures when running ./configure with different arguments than those used by Novell. That way, bugzilla.novell.com can easily become a trash can for all kinds of other people's bugs that don't even affect Novell products at all. Simply go to http://bugzilla.mindrot.org/ after reading http://www.openssh.com/report.html and report that openssh fails to build if both krb5 and libgssapi are installed. Or simply do "rpm -e libgssapi" if you're too lazy, why should others spend more time on such a non-bug? And yes, the openssh source rpm as distributed by Novell is not intended for anything else than being rebuilt in the same environment as the openssh binary packages were built. Why a temporary hack? "Temporary", until what happens? And who maintains your hack until then? Someone familiar with the code base (i.e., an openssh upstream maintainer) should be able to fix that properly, non-temporarily and without breaking the build on other platforms/configurations. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.