It looks as if any changes for the compile breakage caused by
removing SIOCGSTAMP (and perhaps other SIOCG* definitions) from
<sys/socket.h> are being left for upstreams to fix, and perhaps the
next glibc release will include a fix to pull in the new header.
In the meantime, the seds to define SIOCGSTAMP as 0x8906 seem to do
the job. I was concerned that they might be fine for x86 but could
possibly be wrong for other architectures, and we know that people
sometimes use our instructions e.g. for Pi, but apparently the
values are not architecture-specific.
Obviously, different files need to be changed to fix different
programs. But to sprovide a common explanation, could we use a
standard copymember, something like (omitting the markup)
sed -i 's/SIOCGSTAMP/0x8906/' ... : In linux-5.1 the definition of
SIOCGSTAMP was moved and is no-longer in <sys/socket.h>. Hard-coding
its value enables packages which do not know about that change to
continue to compile with current headers.
And perhaps add a ticket "Fixes for SIOCGSTAMP breakage" to note
which packages are affected (I know some are already fixed, but
perhaps use the common explanation).
At this point I don't have a system with 5.2 headers, and I suspect
I'm a couple of weeks away from an up to date build.
ĸen
--
One pill makes you larger, And one pill makes you small.
And the ones that mother gives you, Don't do anything at all.
Go ask Alice, When she's ten feet tall.
-- Jefferson Airplane, White Rabbit
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
