I saw this problem on an old Fedora last week, but I haven't gotten around to 
follow up on it.  Here's a works-for-me patch for 
net-tools-1.60_p20111120203157 and net-tools-1.60_p20120127084908.

See 
http://forum.soft32.com/linux/headers-linux-atm-userspace-build-broken-recent-change-__be1-ftopict338634.html,
 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433962
--- lib/fddi.c.orig     2011-11-20 17:31:57.000000000 -0800
+++ lib/fddi.c  2012-03-07 17:49:14.858321930 -0800
@@ -26,6 +26,7 @@
 #error "No FDDI Support in your current Kernelsource Tree."
 #error "Disable HW Type FDDI"
 #endif
+#include <linux/types.h>
 #if __GLIBC__ >= 2
 #include <netinet/if_fddi.h>
 #else

I guess this is fixed in more recent kernel headers?

// Johan


On 22 Mar 2012, at 08:55, Jeremy Olexa wrote:

> (top posting to avoid confusion)
> 
> Hello,
> 
> The proper place to document and work on build failures is with
> bugs.gentoo.org. If a package is missing a dependancy then we can
> forward it to the proper dev.
> https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%2FAlt (select
> 'Prefix Support')
> 
> Thanks,
> Jeremy
> 
> On Thu, Mar 22, 2012 at 9:33 AM, Nicolas Pinto <[email protected]> 
> wrote:
>> Brent,
>> 
>> I got similar issues a while back, here is something you could try
>> before emerging net-tools:
>> https://github.com/npinto/gentoo-prefix-bootstrap/blob/master/system.mk#L168
>> 
>> HTH
>> 
>> N
>> 
>> On Thu, Mar 22, 2012 at 3:27 PM, Brent Millare <[email protected]> 
>> wrote:
>>> Hello,
>>> 
>>> I'm following the solaris guide for installing gentoo prefix on a red hat
>>> system.
>>> 
>>> /home/bmillare/gentoo-prefix/var/tmp/portage/sys-apps/net-tools-1.60_p20120127084908/temp/build.log
>>> http://pastebin.com/ytrCrYBE
>>> 
>>> /home/bmillare/gentoo-prefix/var/tmp/portage/sys-apps/net-tools-1.60_p20120127084908/temp/environment
>>> http://pastebin.com/MhB695uS
>>> 
>>> /home/bmillare/gentoo-prefix/var/tmp/portage/sys-apps/net-tools-1.60_p20120127084908/work/net-tools-1.60_p20120127084908
>>> http://pastebin.com/imuGuBuv
>>> 
>>> Anyone know how to fix this?
>>> 
>>> Thanks,
>>> Brent


Reply via email to