Compiling librpc/gen_ndr/ndr_libnet_join.c Linking bin/net /usr/lib/gcc/i686-pc-linux-gnu/4.3.4/../../../../i686-pc-linux-gnu/bin/ld: canno t find -lnetapi collect2: ld returned 1 exit status make: *** [bin/net] Error 1 * ERROR: net-fs/samba-3.4.6 failed: * emake binprogs failed * * Call stack: * ebuild.sh, line 54: Called src_compile * environment, line 3042: Called die * The specific snippet of code: * emake ${BINPROGS} || die "emake binprogs failed"; * * If you need support, post the output of 'emerge --info =net-fs/samba-3.4.6', * the complete build log and the output of 'emerge -pqv =net-fs/samba-3.4.6'. * The complete build log is located at '/tmp/portage/portage/net-fs/samba-3.4.6 /temp/build.log'. * The ebuild environment file is located at '/tmp/portage/portage/net-fs/samba- 3.4.6/temp/environment'. * S: '/tmp/portage/portage/net-fs/samba-3.4.6/work/samba-3.4.6/source3' * Messages for package net-fs/samba-3.4.6: * ERROR: net-fs/samba-3.4.6 failed: * emake binprogs failed * * Call stack: * ebuild.sh, line 54: Called src_compile * environment, line 3042: Called die * The specific snippet of code: * emake ${BINPROGS} || die "emake binprogs failed"; * * If you need support, post the output of 'emerge --info =net-fs/samba-3.4.6', * the complete build log and the output of 'emerge -pqv =net-fs/samba-3.4.6'. * The complete build log is located at '/tmp/portage/portage/net-fs/samba-3.4.6 /temp/build.log'. * The ebuild environment file is located at '/tmp/portage/portage/net-fs/samba- 3.4.6/temp/environment'. * S: '/tmp/portage/portage/net-fs/samba-3.4.6/work/samba-3.4.6/source3'
Created attachment 232907 [details] emerge info
gentoo ~ # emerge -avq samba [ebuild R ] net-fs/samba-3.4.6 USE="client* pam server smbclient swat* winbind -acl -addns -ads -aio -avahi -caps -cluster -cups -debug -doc -examples -fam -ldap -ldb -netapi -quota -readline -smbsharemodes -syslog"
Created attachment 232909 [details] samba 3.4.6 build log
Your CFLAGS and CXXFLAGS are a bit agressive. Can you sanitize them and test again please?
(In reply to comment #4) > Your CFLAGS and CXXFLAGS are a bit agressive. Can you sanitize them and test > again please? > Sure. It will take some time. Please be patient!
(In reply to comment #4) > Your CFLAGS and CXXFLAGS are a bit agressive. Can you sanitize them and test > again please? > Same error with sme useflags after these changes: CFLAGS="" CXXFLAGS="${CFLAGS}" ##LDFLAGS="-Wl,-O1 -Wl,--hash-style=both" Looking forward to any idea.
The build error happens because the USE flag combination you are using needs netapi USE flag to be activated. Specifically client USE flag forcibly needs netapi, this affects samba 3.4.6 and 3.4.8, so that restriction has been added to both ebuilds. Thanks for the report.
(In reply to comment #7) > The build error happens because the USE flag combination you are using needs > netapi USE flag to be activated. > > Specifically client USE flag forcibly needs netapi, this affects samba 3.4.6 > and 3.4.8, so that restriction has been added to both ebuilds. > > Thanks for the report. > Checked. Works fine. Thank you so much!