Doh! :-D do de do….

 

I suspect some of the other “broken” packages I found & fixed may also be due to incorrect configuration.

 

 

 


From: gumstix-users-bounces@lists.sourceforge.net [mailto:gumstix-users-bounces@lists.sourceforge.net] On Behalf Of Craig Hughes
Sent: 23 August 2006 17:00
To: General mailing list for gumstix users.
Cc: truckingeek@yahoo.com
Subject: Re: [Gumstix-users] Buildroot problem with NMAP

 

On Aug 23, 2006, at 7:51 AM, <thomas.cooksey@bt.com> wrote:



I’ve also had the exact same thing, but I don’t need nmap so I unselected it. I was using today’s (23/8/06) buildroot.

 

I have also noticed quite a lot of other things are broken in the buildroot tree which I have had to go in and fix. I can give a list of problems & fixes if this would be helpful to anyone?

Yes, absolutely.  The way these things get fixed is when someone fixes them :)



 The most important one springing to mind is the $(PCMCIA_DIR)/.modules.dep target in the pcmcia.mk package makefile: busybox’s depmod.pl takes EITHER the kernel image OR the symbol map, the pcmcia.mk specifies both on the command line and causes the script to abort. Very simple fix, just remove either the

“-k $(LINUX_DIR)/vmlinux \” line or the “-F $(LINUX_DIR)/System.map” line.

You shouldn't be building pcmcia with the 2.6.17 kernel.  You should be using pcmcia-utils instead.  The correct "fix" here is to have a dependency between pcmcia-utils/pcmcia and the kernel version in both config and makefiles I think.


On the subject of pcmcia stuff, is there any plans to create a package for the new pcmcia utils? I keep getting warnings from the kernel that support for the old userspace tools will be removed very soon.

It's already there, and turned on by default.  You have to manually override the default, and fix a broken package in order to get that warning message ;)

 

C