dhcpcd-discuss

---------------------> PLEASE REPLY BELOW THIS MESSAGE <---------------------
From: Kristopher John Gamrat
To: Roy Marples
CC: dhcpcd-discuss@xxxxxxxxxxxx
Date: Thursday 14 February 2019, 11:23:06 pm
Subject: Re: [dhcpcd-discuss] Build error on CentOS 7

On Monday 11 February 2019 at 01:10:45 pm, Roy Marples wrote:
> On 11/02/2019 16:13, Roy Marples wrote:
> > On 08/02/2019 03:16, Kristopher John Gamrat wrote:
> >> ---------------------> PLEASE REPLY BELOW THIS MESSAGE
> >> <---------------------
> >>
> >> I am running CentOS 7 and I have been able to successfully build dhcpcd
> >> v7.0.8, though I had to manually install the hooks as make failed
> >> here. With
> >> dhcpcd v7.1.0 and v7.1.1, I am seeing a complete failure to build. The
> >> output
> >> from `make` is pasted below, along with the output of `uname -a` and
> >> `gcc --version`. Near the bottom of make's output, you'll see a message
> >> related to the hooks, which is the same error I got from 7.0.8, though
> >> this I
> >> can work around manually if needed.
> >>
> >> [piki@localhost]~/rpmbuild/SOURCES/dhcpcd-7.1.1% make
> >> for x in src hooks; do cd $x; make all; cd ..; done
> >> make[1]: Entering directory
> >> `/home/piki/rpmbuild/SOURCES/dhcpcd-7.1.1/src'
> >> cc -O2 -std=c99 -DHAVE_CONFIG_H -DNDEBUG -D_GNU_SOURCE
> >> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> >> -DINET -DARP -DARPING -DIPV4LL -DINET6 -DDHCP6 -DAUTH -I.. -I../src
> >> -I./crypt -c
> >> if-linux.c -o if-linux.o
> >> if-linux.c: In function ‘if_opensockets_os’:
> >> if-linux.c:318:27: error: ‘SOL_NETLINK’ undeclared (first use in this
> >> function)
> >>    setsockopt(ctx->link_fd, SOL_NETLINK, NETLINK_BROADCAST_ERROR,
> >>                             ^
> >> if-linux.c:318:27: note: each undeclared identifier is reported only
> >> once for
> >
> > Someone on the #centos irc channel on Freenode said this:
> > not using our kernel either, try yum install kernel-ml-{devel,headers}
>
> After many discussions in their IRC channel, we concluded it's a missing
> define from glibc and is already fixed in newer versions.
> As RH are very unlikely to fix this, I've added a patch to work around
> this sad issue.
> I've also fixed the make issue, so it should build fine on Centos-7 now.
>
> https://roy.marples.name/git/dhcpcd.git/commit/?id=2e1657edffd718ba3b7882c9
>98e54c0777857d50
> https://roy.marples.name/git/dhcpcd.git/commit/?id=a9c0bec433968247a83b528c
>31c5b4dc9f309e1e
> https://roy.marples.name/git/dhcpcd.git/commit/?id=edb38a968396f57478869773
>587eab6a26bc01cf
>
> Let me know if this fixes it for you!
>
> Roy

Those patches seem to fix things, but with one oddity: `make install` seems a 
bit confused on which hook to use for ypbind. It installs 50-ypbind.in even 
though a comment near the top of that file says it is for BSD, and a similar 
comment near the top of 50-yp.conf says it is for Linux (what I'm using).

(hopefully RH and Debian will figure out soon that "stable" doesn't mean 
hiring software archaeologists :-) certainly, I can understand why they tend 
to be a bit behind, but still...)

-- 
Kristopher Gamrat
Jabber ID: chaotickjg@xxxxxxxxxx
My OpenPGP Key Fingerprints:
CBB4 4C0B 7794 F668 D486 9B68 02C0 8EE2 7F03 0E92

May you be blessed by Our Holy Glob the FSM.

----------------------------- FRIENDLY REMINDER -----------------------------

> On Tuesday, January 02, 2666 at 12:02:46 PM, Kris said:
> > 
> > On Monday, January 01, 2666 at 13:13:13 PM, Kris' Evil Twin said:
> > > 
> > > Why do you want me to reply below quotes?
> > 
> > > On Sunday, December 31, 2665 at 10:32:46 AM, Kris said:
> > > > 
> > > > Please reply below quotes.
> > > > 
> > Because:
> >  * it helps avoid confusing email quotes like this example
> >  * it makes it easier to match the quote dates to the quotes
> >  * it makes it easier for us to truncate quotes without messing up the
> >    quote dates or the ordering of the quotes
> >  * it makes it easier for the me to see what you are replying to (because
> >    it's the very first thing I see in your message)
> >  * it makes it easier for me to reference the quote of your message when I
> >    am typing my reply (because it's the last thing in your message and
> >    immediately above where my email client has me type my message)
> > 
> > Thank you for understanding.
> > 

---------------------> PLEASE REPLY BELOW THIS MESSAGE <---------------------

Attachment: signature.asc
Description: This is a digitally signed message part.