FS#1310 - e2fsprogs/libext2fs breaking krb5 #5829
Comments
|
nwf: I have some patches that make the krb5 build use the e2fsprogs com_err and et libraries. I haven't tried using them in a while, but here they are for review. I know others have similar fixes, too. |
|
Andy2244: thx will try those! |
|
Andy2244: Seems to still work after adapting them to krb5-1.16 and the current e2fsprogs makefile. Thx a bunch, will setup a pull-request, so i can hopefully get my samba4.8 package merged too, which did break because if this. |
|
nwf: Rock! Thanks for exerting the effort to get these upstreamed. If you need changes made to them, don't hesitate to ping me (though perhaps use github, since flyspray doesn't seem to have an easy way to see what's been modified recently or notifications or any such?) |
|
Andy2244: Yeah had the same problem, they just disable notify by default. |
|
jow-: I cleaned up your original patch submission and committed it with https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=20d63ebc942012040e08bb815a94f40e535b9cf9 to the tree. |
Andy2244:
Basically libext2fs dont cares if there are already existing system libs (libcom_err.so, libe2p.so, libss.so) and installs its own versions. The package also does not provide a dev/install (usr/bin/compile_et) so other packages can at least try using it.
As example package/krb5 can be build with "--with-system-et" yet, even if we copy the e2fsprogs compile_et and supply it via "ac_cv_prog_compile_et=$(STAGING_DIR)/usr/bin/compile_et" its incompatible with what krb5 expects.
So if e2fsprogs is build after krb5, the krb5 libs break and are unusable or any other package that uses com_err.
So the build system libs should probably be static linked and libcom_err, libe2p, libss should not be installed.
The text was updated successfully, but these errors were encountered: