Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)
Joakim Tjernlund
Fri Jan 11 11:31:37 2019
On Fri, 2019-01-11 at 09:17 +0000, Roy Marples wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On 10/01/2019 22:21, Stefano Cappa wrote:
> > I'm building dhcpcd in Yocto 2.6 (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.yoctoproject.org%2F&data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7Cc1051cdaa39840bd88a008d677a59fa1%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636827950577299766&sdata=DrLv6JucU29BQNtzqlFcX1GiVDZkGe64%2F8O%2FPO4vG%2BM%3D&reserved=0), with
> > open-embedded to add the porting of dhcpcd
> > (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flayers.openembedded.org%2Flayerindex%2Frecipe%2F93064%2F&data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7Cc1051cdaa39840bd88a008d677a59fa1%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636827950577299766&sdata=MVnk7T55syK3PYycuevhTemA6SdizJ%2FqHq3aWSLq8BI%3D&reserved=0).
> > Version 6.11.5 is ok, but when I try to change the bitbake recipe
> > (https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcgit.openembedded.org%2Fmeta-openembedded%2Ftree%2Fmeta-networking%2Frecipes-connectivity%2Fdhcpcd%2Fdhcpcd_6.11.5.bb%3Fh%3Dthud&data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7Cc1051cdaa39840bd88a008d677a59fa1%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636827950577299766&sdata=IzWQ96jdJBWWBYIuZvLX%2BlqJALJbRwGISzO2iPfehAw%3D&reserved=0)
> > to port it to 7.0.8, I receive that error.
> > I also opened a discussion in the official mailing list
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Fpipermail%2Fyocto%2F2019-January%2F043755.html&data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7Cc1051cdaa39840bd88a008d677a59fa1%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636827950577299766&sdata=41hYCVptEdVPZPNCsNoCCsGb2wqlwE96VNymryIUXPo%3D&reserved=0
>
> This is passed to configure: --includedir=/usr/include
>
> That is exactly what the compiler then complains about.
> So fix the build environment .... how I have no idea, but good luck!
>
> > | ./configure: WARNING: unknown option --exec_prefix
> > | ./configure: WARNING: unknown option --sharedstatedir
> > | ./configure: WARNING: unknown option --oldincludedir
> > | ./configure: WARNING: unknown option --with-libtool-sysroot
I think you have old autotool/libtool which was used to generate this configure.
--with-libtool-sysroot is a modern libtool feature, needed for cross building.
>
> These are not supported and passing --includedir=/usr/include may rely
> on them working .... so yeah, remove --includedir=/usr/include from the
> configure
Yes, why add /usr/include in the first place?
>
> > | ./configure: WARNING: unknown option --with-udev
>
> You can't turn udev on explicitly, you can only turn it off.
"On" should be an option too and configure should fail if it doesn't find udev
Jocke
Archive administrator: postmaster@marples.name