On Mon, 2007-03-26 at 19:41 -0400, Mike Frysinger wrote: > On Monday 26 March 2007, Al Stone wrote: > > My initial thought was to create a new configuration variable > > (UCLIBC_DEBIAN_WORKAROUND?) that's off by default, with an #ifdef > > in sysdeps/linux/$ARCH/kernel_types.h around the duplicate -- > > just removing the additional typedef doesn't seem like a good > > idea since it would likely break builds on non-Debian systems. > > yikes ! we dont want to have any distro-specific stuff in uClibc in any of > the source files that go into the library ... especially not any transient > ones ...
...and hence the question. It sure _seemed_ like a bad idea. > > Is there a better/preferred way to handle such things? In the > > meantime, Debian bug#415095 has also been filed with a patch that > > includes a fix for the problem, but I'd rather not depend on the > > Debian release schedules to be able to get uClibc working.... > > i guess you're building uClibc on ia64 and by using `gcc` rather than a > dedicated cross-compiler ... tbh, i think your best course of action is to > grab linux-2.6.20 and run `make headers_install` yourself and then point the > uClibc build system at that D'oh. Right -- I'm building where host == target. OTOH, leave it to me to forget the obvious solution, which I was going to need to do later anyway. Must get more coffee.... -- Ciao, al ---------------------------------------------------------------------- Al Stone Alter Ego: Open Source and Linux R&D Debian Developer Hewlett-Packard Company http://www.debian.org E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] ---------------------------------------------------------------------- _______________________________________________ uClibc mailing list [EMAIL PROTECTED] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
