dhcpcd-discuss

Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)

Roy Marples

Fri Jan 11 13:47:28 2019

On 11/01/2019 13:27, Joakim Tjernlund wrote:
On Fri, 2019-01-11 at 12:41 +0000, Roy Marples wrote:

On 11/01/2019 11:32, Joakim Tjernlund wrote:
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.

This is hand rolled configure - it's not GNU configure, autotool or libtool.
The way dhcpcd is configured and built works fine in Gentoo Portage
which is a cross build environment - all you really need to do is
specify your cross compiler with the CC env var or --CC= configure option.

I am on Gentoo as well :) It works well because on Gentoo uses gcc's builtin sysroot.
However, one can pass EXTRA_ECONF=--sysroot=/x/y/x if you want a different sysroot.

Or we can stop adding so many knobs and just use CFLAGS?
Example Makefile directive - no idea how to do this in bitbake.
CFLAGS+=	--sysroot=/x/y/x

Maybe the faulty /usr/include below is a result of missing sysroot support ?

./configure: WARNING: unknown option --with-libtool-sysroot
dhcpcd doesn't even use libtool, so there won't be any support for that.

   > | ./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

As you wish:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froy.marples.name%2Fgit%2Fdhcpcd.git%2Fcommit%2F%3Fid%3D2baa28fe39f3c1e780f8b1585c0ca518241f9677&data=02%7C01%7CJoakim.Tjernlund%40infinera.com%7Cc8c024b6a45b4507917408d677c22da9%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636828073214383492&sdata=QlhNFxB262Ww1Urn937%2BGuMpSr4KMAH0%2F%2Fj4yqiP3l8%3D&reserved=0

:) You are way too fast for me

I aim to please :)

Roy

Follow-Ups:
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Joakim Tjernlund
References:
Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Stefano Cappa
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Roy Marples
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Stefano Cappa
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Roy Marples
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Stefano Cappa
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Roy Marples
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Joakim Tjernlund
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Roy Marples
Re: Dhcpcd 6.11.5 - did not receive 2 announcements after 3 unanswered probes (as RFC 5227)Joakim Tjernlund
Archive administrator: postmaster@marples.name