Created attachment 456264 [details] build.log I think the error that kills it is, ldap/servers/slapd/ch_malloc.c:407:5: error: 'for' loop initial declarations are only allowed in C99 or C11 mode for (size_t i = 0; i < n; i++) { I emerged it with no USE flags: $ USE="-bitwise -dna -ldapi -pam-passthru" emerge -pv1 389-ds-base ... [ebuild N ~] net-nds/389-ds-base-1.3.5.15::gentoo USE="-auto-dn-suffix -autobind -bitwise -debug -dna -doc -kerberos -ldapi -pam-passthru -presence (-selinux)" 0 KiB
Created attachment 456266 [details] emerge --info
https://fedorahosted.org/389/ticket/49068 We have already been notified, and we will put the patch in soon. If you wish to resolve the issue, you can patch by adding AC_PROG_CC_STDC to configure.ac and then hashing / emerging. Alternately, you can add -std=c99 for the cflags of the 389-ds-base build. Apologies for the inconvenience. We will try to create a temporary patch to put into the ebuild tree to correct this.
(In reply to William Brown from comment #2) > https://fedorahosted.org/389/ticket/49068 > > We have already been notified, and we will put the patch in soon. > I was trying to do a security audit of the init script -- I don't really need to have this built right away, so there's no rush. But thanks for the quick response.
Thanks. We have created and tested the patch to the ebuild already. I'm waiting for the co-maintainer to do the rest of the process now. If you do find anything during your review please contact me at wibrown at redhat.com so that we can rectify any security issues. Your interest in this is greatly appreciated.
https://github.com/gentoo/gentoo/pull/3154
Created attachment 456748 [details] post-pr-build.log.xz With the new revision, I get... a different build failure =) The new log is attached. I think the first error to appear is, /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../../x86_64-pc-linux-gnu/bin/ld: error: cannot open /var/tmp/portage/net-nds/389-ds-base-1.3.5.15-r1/work /389-ds-base-1.3.5.15/.libs/libns-dshttpd.so: No such file or directory That one is followed quickly by, libtool: error: error: relink 'libacl-plugin.la' with the above command before installing it
Hi, bugs.gentoo.org is not allowing me to access the build log. Additionally, I am unable to reproduce this issue. My first advice (which I'm sure you have taken) is to run a clean on the working directory for the emerge. Following that, I think that this represents a new bug: This is in a different section of the code than the change I introduced to resolve the issue (c99 mode to fix a for loop in libpw.so vs a build issue in libacl.so.). If you can still reproduce this, can you open it in a new bug instead? Otherwise, I think that this is now resolved.
