John Burrell wrote: > > I'm building on LFS-SVN-20120806. > > when compiling net-tools-CVS_20101030 I get this: > > make[1]: Entering directory > `/usr/src/networks/net-tools/net-tools-CVS_20101030/ > lib'
> cc -O2 -g -Wall -fno-strict-aliasing -I.. -I../include -D_GNU_SOURCE -I. > -I/us > r/src/networks/net-tools/net-tools-CVS_20101030/include -Ilib -c -o tr.o tr.c > tr.c:23:25: fatal error: linux/if_tr.h: No such file or directory > compilation terminated. > make[1]: Leaving directory > `/usr/src/networks/net-tools/net-tools-CVS_20101030/lib' > make[1]: *** [tr.o] Error 1 > make: *** [libdir] Error 2 > make[1]: Entering directory > `/usr/src/networks/net-tools/net-tools-CVS_20101030/ > lib' > In tr.c there is this header include: > > #include <linux/if_tr.h> > > I assume that linux-3.5 headers no longer install /usr/include/linux/if_tr.h > > If I change the include to use the netinet if_tr.h which was installed by > glibc - > > #include <netinet/if_tr.h> it compiles, but I don't know if > /usr/include/netinet/if_tr.h is the same as the old > linux/if_tr.h. > > So over to you - is the glibc version compatible or should the required > if_tr.h come from a different source? Looking at linux/if_tr.h and netinet/if_tr.h, they appear to be quite similar. What this header does is define structures constants for token ring interfaces. If it compiles, it is highly unlikely that it would affect you if the code was incorrect. However, it looks like s|linux/if_tr.h|netinet/if_tr.h| is the way to go. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
