Keith, while you were away, the following problem with your kbuild-2.5
patch came up.
Up to now, I tried to get kbuild-2.5 to work on RH7, RH7.1 and a rather
outdated distro, and I didn't get it to work anywhere. Well, the one based
on RH5.2 is just too old I guess (no nftw at all), and on RH7 it seems
that nftw is broken as shipped.
On 7.1 I get
...
Generating global Makefile
phase 1
Command terminated by signal 11
(pp_makefile1 segfaults).
I didn't look into to it any further, yet.
--Kai
BTW, I have an own solution for a new kbuild, which isn't nearly as
mature as yours yet, but it doesn't need any magic C programs and it
handles all dependencies really right, including modversions. Maybe we can
work together to get the best from both approaches at some point.
On Sun, 15 Apr 2001, Kai Germaschewski wrote:
> On Sat, 14 Apr 2001 [EMAIL PROTECTED] wrote:
>
> > [ohio] /usr/src/linux-2.4.3-kb> make -f Makefile-2.5
> > Generating global Makefile
> > phase 1
> > Unexpected type for kernel file .fs, giving up
> > Command exited with non-zero status 1
> > 0.01user 0.00system 0:00.01elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k
> > 0inputs+0outputs (111major+16minor)pagefaults 0swaps
> > make: *** [/usr/src/linux-2.4.3-kb/.tmp_global_makefile_in.1] Error 1
>
> Just wanted to add an "same here" (also RH7).
>
> > I've tracked this error down to the nftw call on my updated RedHat-7.0
> > machine. Apparently, it is not at all pleased with the call nftw(".", ...)
> > - using a walk on the current directory causes all files to be returned
> > using the flag FTW_NS (a non stat'able file). My machine is using the
> > following:
>
> I suppose nftw is broken on RH7. I think it's weird it returns ".fs"
> instead of "./fs" or "fs", which is most likely the cause. On my other,
> older machine, kbuild doesn't work either, btw. (no nftw at all).
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
