dhcpcd-discuss

John,
the f2fs issue aside: how did you compile dhcpcd on a recent Raspbian Jessie? When I tried a few months ago I ran in all kind of problems, starting with header files, and sigsegs. And then I noticed that the Raspbian version 6.7.1 places its hook scripts in different places than stock dhcpcd, the systemd service unit seems to differ, ...
Since I'm still working with 6.7.1 I'm really interested in getting a recent dhcpcd compiled, best if it integrates with Raspbian in the same way as 6.7.1. Can you please shed some light on this?
Thank you very much in advance!Harald


-------- Ursprüngliche Nachricht --------
Von: JED <John@xxxxxxxxxxxxx> 
Datum: 05.05.17  23:25  (GMT+01:00) 
An: dhcpcd-discuss@xxxxxxxxxxxx 
Betreff: [dhcpcd-discuss] Compiling beta3 on Raspberry Pi 

I'm trying to shoot a bug on my Raspberry Pi where dhcpcd has SEGV when 
I convert root file system to f2fs. Why running on f2fs instead of ext4 
breaks dhcpcd I have NO idea, but I'm not sure I care. BTW, I get this:
> May  4 01:27:33 rasp8apr systemd[1]: dhcpcd.service: main process exited, code=killed, status=11/SEG

I'm trying 7.0.0-beta3 to avoid shooting an old bug, since the latest 
Raspbian
> Raspbian Jessie with PIXEL
> Image with PIXEL desktop based on Debian Jessie
> Version: April 2017
> Release date: 2017-04-10
> Kernel version: 4.4
uses
> root@rasp8apr:~# dhcpcd --version
> dhcpcd 6.7.1
> Copyright (c) 2006-2015 Roy Marples
and you've fixed LOTS of things since then. If this is the wrong way to 
proceed, I'm ready for any suggestions.

However
> root@rasp8apr:~/dhcpcd-7.0.0-beta3# ./configure
> configure args:
> Deriving operating system from ... armv7l-unknown-linux
> Configuring dhcpcd for ... linux
> Enabling INET support
> Enabling ARP support
> Enabling ARPing support
> Enabling IPv4LL support
> Enabling INET6 support
> Enabling DHCPv6 support
> Enabling Authentication
> Using compiler .. cc
> cc (Raspbian 4.9.2-10) 4.9.2
> dhcpcd-definitions.conf will be embedded in dhcpcd itself
> Testing for nl80211 ... yes
> Testing for IN6_ADDR_GEN_MODE_NONE ... no
> Testing for getifaddrs ... no
> libc support for getifaddrs is required - aborting

What do I need do to fix this? Web searches turned up this message in 
different versions of this script but no answers.

BTW: Your ftp server seems to not support passive ftp, perhaps because 
of closed ports. I just used https instead. Example of that problem, but 
you probably don't care too much and I worked around it...
> root@rasp8apr:~# wget ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz
> converted 'ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz' (ISO-8859-1) -> 'ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz' (UTF-8)
> --2017-05-05 12:33:06--  ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz
>            => 'dhcpcd-7.0.0-beta3.tar.xz'
> Resolving roy.marples.name (roy.marples.name)... 81.108.15.115
> Connecting to roy.marples.name (roy.marples.name)|81.108.15.115|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/dhcpcd ... done.
> ==> SIZE dhcpcd-7.0.0-beta3.tar.xz ... 203440
> ==> PASV ... couldn't connect to 10.73.2.61 port 49001: Connection timed out
> Retrying.
>
> --2017-05-05 12:35:20--  ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz
>   (try: 2) => 'dhcpcd-7.0.0-beta3.tar.xz'
> Connecting to roy.marples.name (roy.marples.name)|81.108.15.115|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/dhcpcd ... done.
> ==> SIZE dhcpcd-7.0.0-beta3.tar.xz ... 203440
> ==> PASV ... couldn't connect to 10.73.2.61 port 49005: Connection timed out
> Retrying.
>
Just to see, I later told wget --no-passive-ftp and that works, too. It 
just took me a while to find that option in the 1440 lines of man file, 
since PASV wasn't in there and I had to remember exactly what that was 
about. Memory is the second thing to go.