-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sssd-2.4.2: build using autoconf 2.71 fails #5563
Comments
Hi, what is the output of
? Or Did you run |
and output of that part of the build procedure:
(seems I can remove --with-crypto but that is not relevant)
and none of them can affect samba detection. |
Do You have |
Of course I have buit looks like somethiong is concatenation |
BTW why not use pkgconfig for samba detection?
|
Just found src/external/samba.m4 so looks like already pkgconfig is used but for some reasons not to detect samba version (?) .. hm. |
What's your version of |
On my system output is weird:
|
I'm usimg autoconf 2.71. |
Hi @ikerexxe, did you see something similar while working on https://bugzilla.redhat.com/show_bug.cgi?id=1943130 ? |
Simailar configure errors as in #5502 |
Yes. Once I included the changes from #5495 in the mock build, the configuration errors from #5336 disappear and the ones related with |
Are you using some special environment, like chroot, to build sssd? |
|
Which distribution and version are you using? |
My own :) |
sssd build with an autoconf version greater than 2.70 fails because CPP macro is empty. This change fixes this problem by setting the macro with AC_PROG_CPP at the beginning of the configuration. Resolves: SSSD#5563
I think that I solved the problem in PR5573, at least that's my case. Can you check if it works for you too? |
#5573 works for me. Feel free to cloese that ticket. |
sssd build with an autoconf version greater than 2.70 fails because CPP macro is empty. This change fixes this problem by setting the macro with AC_PROG_CPP at the beginning of the configuration. Resolves: SSSD#5563 Reviewed-by: Sumit Bose <sbose@redhat.com>
The text was updated successfully, but these errors were encountered: