find . -path './scripts/*' -prune -o -path './Documentation/*' -prune -o \
-path './debian/*' -prune -o -type f \
\( -name 'Makefile*' -o -name 'Kconfig*' \) -print | \
cpio -pd --preserve-modification-time $(HEADER_SRC);
it was "Makefile" before and I changed to "'Makefile*'"
this is a bumpy road
you see why I'm happy you're doing it this time
I certainly do :)
I remember the 'old' days when you actually ran 'make menuconfig && make bzImage && make modules && make modules_install'
that was EASY
oh,btw.. did you know there is no ADEOS any more?
CONFIG_ADEOS & such
oh is that IPIPE now?
I kept looking and looking :)
I don't understand the difference but I know for a while both have been options
and it seems make-kpkg is kinda borked for making custom kernels
lucky me there was a guy in #ubuntu-kernel who tried my first kernel out, and found out why there is no usplash
that's the whole point of make-kpkg
not that I disagree with you
Because initramfs-tools isn't finding any framebuffers in /initrd/, it's not
23:02 < infinity> No fbcon, no usplash.
he told me a way to make a custom post-install script
to convince make-kpkg to do the needed stuff
something is borked.. check this out:
doesn't quite seem like the right path.. does it?
hmm.. might have borked the rtai-path
when I run the make-kpkg .. modules_image
I get an menuconfig for rtai eventually
what paths do I put in there?
are you using the same rtai as I used?
maybe there are udev fixes in rtai cvs
hmm.. then I need to debianize it..?
iirc you just use dmake and then fix up its generated files
I also did madwifi that way
dmake: Executing shell macro: $(srctree)/base/config/autoconf/config.guess
dmake: makefile: line 20: Error: -- /base/config/autoconf/config.guess: No such file or directory
dmake: Error code -1, while making 'Shell escape'
maybe I should run ./configure first?
hmm.. there is a makefile..
sorry I don't remember
was it dmake?
ii dmake 4.3+cvs2006010 make utility used to build OpenOffice.org
there's one that makes the debian directory for you
I think that's for building
debmake - helper package for debian/rules (deprecated)
Then dh_make proceeds to generate a "debian" subdirectory and the nec-
essary control files in the program source directory. Those control
files are customized with the packagename and version extracted from
what a mess
all package management systems suck
rpm is even worse than deb
I guess 'kernel module' right?
dh_make is asking what package..
cradek: your patch produces a Module.symvers, right?
so that module builds don't complain..
during the rtai build, I see the file vanish, and a new oen appears called __Module.symvers
* alex_joni is talkign about /usr/src/linux-headers-2.6.15-magma/Module.symvers
just an empty file
yeah, but it gets renamed for who knows what reason
do you have modversions etc turned off?
you started with my .config right?
yes, I do
I didn't manage to start with yours.. too many differences.. but I have all the relevant stuff in there
I'm having a bit of a problem now..
can't figure out what you meant here:
cp debian/$(PKGNAME)/usr/src/modules/rtai-3.3/debian/rtai-modules-2.6.12-magma/usr/realtime-2.6.12-magma/modules/*.ko $(CURDIR)/debian/$(PKGNAME)$(RTAI_PREFIX)/modules
rm -r debian/$(PKGNAME)/usr/src
probably the rtai makefiles put stuff in the wrong place
obviously the first path it installs to is bogus
so I guess that was my way of fixing it
but I don't see that path here..
probably you missed a control file or whatever
I commented out those 2 lines, and trying again :)