Created attachment 714762 [details] build.log Fails to build with USE=ppp despite ppp being installed. [ebuild R ] net-dialup/ppp-2.4.9-r2:0/2.4.9::gentoo USE="eap-tls ipv6 pam -activefilter -atm -dhcp -gtk -radius" 0 KiB [...] checking for NSS... yes checking pppd/pppd.h usability... no checking pppd/pppd.h presence... no checking for pppd/pppd.h... no configure: error: "couldn't find pppd.h. pppd development headers are required." !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-misc/networkmanager-1.30.4/work/NetworkManager-1.30.4-abi_x86_64.amd64/config.log * ERROR: net-misc/networkmanager-1.30.4::gentoo failed (configure phase): * econf failed
Created attachment 714765 [details] emerge --info
The problem is related to ppp. It search ppp_deps.h inside include/net when it is in include/linux. Opened a PR upstream to fix it: https://github.com/ppp-project/ppp/pull/293
There were several of this 'family' of bugs eg 713392 and 713466 which I'd thought had been solved wrt ppp. Does this 'style' of fix apply elsewhere too? I've actually got a job pending to push the Gentoo patchset upstream also (there's a PR for 2.4.9 release with comments I won't link here) but that's separate.
(In reply to Michael 'veremitz' Everitt from comment #3) > There were several of this 'family' of bugs eg 713392 and 713466 which I'd > thought had been solved wrt ppp. Does this 'style' of fix apply elsewhere > too? > > I've actually got a job pending to push the Gentoo patchset upstream also > (there's a PR for 2.4.9 release with comments I won't link here) but that's > separate. This fix is for all these packages that require it. I'm sure that ppp_defs.h was on net/ until some point (i haven't checked it) and that's because it was set like that. I have also the idea that glibc has it internally and that's why glibc users does not have such problem
Also no one changed it since 1994, https://github.com/ppp-project/ppp/commit/a3396b002507d72b3e1f1169bd02ae018539654b#diff-42a0dd69046ea1e7a1aa82bbec76ae7c90eaf4dea269e9cb779701cbd045ad4b
*** Bug 821646 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 853760 ***