On Sat, Jun 21, 2014 at 11:08:19AM -0400, squidmobile at fastmail.fm
wrote:> 21 jun 2014
>
> the version numbers changed (samba-4.1.8), but the problem
> remains exactly the same: waf configure continues to break at
> krb5.
Please attach bin/config.log.
Cheers,
Jelmer
> frank smith
>
>
> 31 may 2014
>
> greetings,
>
> in the (relatively distant) past, i several times downloaded,
> built, and ran the then-current version of samba with little to no
> problem. i recently experienced similar successful results with
> samba-3.6.23.
>
> i downloaded and tried to configure samba-4.1.7, which you (samba)
> advertise as the current "stable" version. i expected no
problems.
> unfortunately, i encountered major problems with waf.
>
> ./configure (which points to ./buildtools/bin/waf configure)
> reports this when it gets to mit krb5:
>
> ...
> Looking for kerberos features
> Checking for program krb5-config.heimdal : not found
> Checking for program krb5-config :
> /local/bin/krb5-config
> Checking for /local/bin/krb5-config : yes
> Checking for gssapi : yes
> Kerberos 5 release 1.12.1 is detected, MIT krb5 build can proceed
> Checking for com_err : yes
> Checking for library com_err : yes
> Checking for _et_list : ok
> Checking for header com_err.h : yes
> Checking for header krb5.h : yes
> Checking for header krb5/locate_plugin.h : yes
> Checking for header gssapi.h : yes
> Checking for header gssapi/gssapi_generic.h : yes
> Checking for header gssapi/gssapi.h : yes
> Checking for header gssapi/gssapi_ext.h : yes
> Checking for header gssapi/gssapi_krb5.h : yes
> Checking for library k5crypto : not found
> Checking for krb5_encrypt_data : not found
> ...
>
> /local/bin/krb5-config --libs --cflags reports:
> -I/local/package/krb5-1.12.1/include
> -L/local/package/krb5-1.12.1/lib -Wl,--enable-new-dtags -Wl,-rpath
> -Wl,/local/package/krb5-1.12.1/lib -lkrb5 -lk5crypto -lcom_err
>
> running ./configure with the -v option gives this interesting dialog:
>
> Checking for header gssapi/gssapi_krb5.h :
> 21:53:04 runner /usr/bin/gcc -MD -I/usr/local/include
> -I/local/package/krb5-1.12.1/include -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1
> -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../test.c -c -o
> default/test_1.o
> yes
>
> Checking for library k5crypto :
> 21:53:04 runner /usr/bin/gcc -MD -I/usr/local/include -D_SAMBA_BUILD_=4
> -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../test.c
> -c -o default/test_1.o
> 21:53:04 runner /usr/bin/gcc default/test_1.o -o
>
/scratch01/gigo.d1/gigo.d/samba-4.1.7/bin/.conf_check_0/testbuild/default/testprog
> -fstack-protector -Wl,-no-undefined -L/usr/local/lib -Wl,-Bdynamic
> -lk5crypto
> not found
>
> i find it peculiar that the gssapi/gssapi_krb5.h test used the
> proper -I flag, but the k5crypto test included NEITHER the
> proper -I flag nor the -L flag. nor did it find -lk5crypto
> in the location indicated by /etc/ld.so.conf and ldconfig -p ...
>
> your waf program set flags that broke the subsequent waf build
> process.
>
> i think i ran into similar problems with it not finding openldap.
>
> btw- i find it interesting/amusing that your waf program loved
> the /usr/local/include and /usr/local/lib directories even though
> they contain absolutely nothing...
>
> begin soapbox diatribe:
> i have run into waf in more than one package. EVERY time, waf
> screws up to the point where its package will NOT compile at all.
> i wish you would go back to the traditional ./configure program
> that works well countless times with countless packages.
> end soapbox mode.
>
> please correct your dependency upon fixed locations
> (/usr/local/...) and restore the flexibility provided by
> --with-package-dir=/some/tree/package.
>
> the frustrated
> frank smith
>
> --
> http://www.fastmail.fm - Choose from over 50 domains or use your own
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20140621/d2977769/attachment.pgp>